Add Elaine Wang profile to team page - #77
Conversation
Co-authored-by: Kristen Aiemjoy <16113030+kaiemjoy@users.noreply.github.com>
| Elaine is a 1st year MS student in the Applied Mathematics program at UC Davis. Her current research focuses on developing the `serodynamics` R package, which extends the Serocalculator framework to support broader seroepidemiological modeling of antibody dynamics. Her research interests lie at the intersection of statistical and mathematical modeling and infectious disease epidemiology, with a focus on disease forecasting and prevention in global health settings. | ||
|
|
||
| Email: yxewang@ucdavis.edu | ||
|
|
There was a problem hiding this comment.
| possibly add github id |
| institution: "UC Davis" | ||
| --- | ||
|
|
||
| Elaine is a 1st year MS student in the Applied Mathematics program at UC Davis. Her current research focuses on developing the `serodynamics` R package, to support broader seroepidemiological modeling of post-infection antibody dynamics. Her research interests lie at the intersection of statistical and mathematical modeling and infectious disease epidemiology, with a focus on disease forecasting and prevention in global health settings. |
There was a problem hiding this comment.
| Elaine is a 1st year MS student in the Applied Mathematics program at UC Davis. Her current research focuses on developing the `serodynamics` R package, to support broader seroepidemiological modeling of post-infection antibody dynamics. Her research interests lie at the intersection of statistical and mathematical modeling and infectious disease epidemiology, with a focus on disease forecasting and prevention in global health settings. | |
| Elaine is a 1st year MS student in the Applied Mathematics program at UC Davis. Her current research focuses on developing the `serodynamics` R package, to support broader seroepidemiological modeling of post-infection antibody dynamics. Her research interests lie at the intersection of statistical and mathematical modeling and infectious disease epidemiology, with a focus on disease forecasting and prevention in global health settings. |
|
Thanks! Both suggestions applied. Ready for re-review. |
|
@kaiemjoy just a gentle bump — ready for re-review whenever you have time! |
kaiemjoy
left a comment
kaiemjoy
left a comment
There was a problem hiding this comment.
looks great, thanks Elaine
|
@claude review the error |
|
Claude Code is working… I'll analyze this and get back to you. |
rossjrw/pr-preview-action v1 does not support fork PRs: the GITHUB_TOKEN issued for pull_request events from forks is read-only and cannot push to gh-pages, so the deploy step always fails with a 403 for those PRs (e.g. PR UCD-SERG#77 from imelainew's fork). Skip the whole job when the PR head repo isn't this repo instead of failing CI.
claude-code-review.yml can't work for fork PRs: pull_request events from forks never receive an OIDC token at all (GitHub never sets ACTIONS_ID_TOKEN_REQUEST_URL for them, regardless of id-token: write - confirmed on PR UCD-SERG#77, run 30686460528/job/91333167166), and switching to pull_request_target doesn't help either since Anthropic's token-exchange endpoint rejects OIDC tokens minted under that event (UCD-SERG#89, anthropics/claude-code-action#713). issue_comment is subject to neither restriction. Add a workflow, gated to OWNER/MEMBER/COLLABORATOR commenters, that a maintainer can trigger with "@claude review" on any PR - fork or not - to get the same review claude-code-review.yml gives same-repo PRs.
|
@claude review Generated by Claude Code |
|
Claude Code is working… I'll analyze this and get back to you. |
Fixes a blocking defect introduced by the previous round's own fix, and a factual claim I published in three places. - BLOCKING: the dispatch always passed `--ref "$PR_BRANCH"`, and a workflow_dispatch runs the workflow file as it exists at that ref. This PR is what ADDS the workflow_dispatch trigger, so every branch cut before it lacks it -- three of the four open same-repo PRs. Either the dispatch is rejected and `set -e` kills the step before the acknowledgment posts, or it runs a copy that selects no job and the acknowledgment posts anyway, reintroducing the false promise the fork short-circuit was added to prevent. Now tries the PR branch, falls back to a no-ref dispatch, and acknowledges only if one actually started a run -- reporting the failure on the PR otherwise. Removing upstream's REF_ARGS array last round had also removed the only no-ref path, which is what left a deleted head branch with no fallback. - FACTUAL: "it never executed once (5/5 runs skipped)" was wrong. That came from reading `--limit 5` and generalizing to the population. The real history is 25 runs: 23 skipped, one still in flight, and one success -- run 30687108541 on 2026-08-01, against fork PR #77, the exact case the workflow was written for. It executed and posted nothing because its prompt never carried `--comment` (#96), which #97 fixed for the other review workflow and never for this one. The justification for deleting it is that it was non-functional, not that it never ran. - FACTUAL: the user-facing fork notice blamed the OIDC exchange. That is the `pull_request`-path story (#90); a dispatched run executes in base-repo context with no fork token involved, and upstream describes its guard as failing a mistaken dispatch fast rather than closing a hole. - "produces no run at all" corrected -- a skipped run is still recorded. - `pull-requests: read` restated as declared rather than required, since a public repo would permit the read anyway. - The `pull-requests: write` rationale covered only the pull_request trigger; added what bounds the workflow_dispatch path. - Disambiguated "Set this to true", which sat five lines from its referent with `require-review` as the nearer antecedent, and split the three unrelated paragraphs sharing one heading. - report-cost's description corrected to "appends". Refs #101
|
/review |
|
@claude review |
|
👀 Picked up by workflow run #32804452985. Setup runs first; Claude itself responds after that. |
Code review (stand-in)Posted in response to the review request on this thread. The repo's automated reviewer cannot reach this PR by any trigger: it is a fork PR, and both the Reviewed commit: The content is in good shape. kaiemjoy's suggestions were verified applied at the current head rather than taken from the "addressed" replies: the bio paragraph matches the corrected suggestion verbatim, and the requested GitHub id is present and resolves. The 2026-07-30 approval covers the current content -- every commit since is a 1.
|
There was a problem hiding this comment.
Pull request overview
Adds a new lab member profile (Elaine Yuxuan Wang) and wires it into the existing Quarto-based team listing so it appears on the Team page.
Changes:
- Added a new bio page at
people/yxewang/bio-yxewang.qmdwith front matter compatible with the existing people templates. - Added a profile photo at
people/yxewang/yxewang.jpgand referenced it from the bio. - Updated
team.qmdto include the new bio in thelab-memberlisting contents.
Reviewed changes
Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| team.qmd | Adds the new bio file to the lab-member listing so the profile appears on the Team page. |
| people/yxewang/bio-yxewang.qmd | Introduces Elaine’s profile page (front matter + bio content) in the established format. |
| people/yxewang/yxewang.jpg | Adds the portrait image referenced by the new bio page. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Adding my profile to the lab team page as requested.
Changes:
people/yxewang/bio-yxewang.qmd(bio)people/yxewang/yxewang.jpg(profile photo)team.qmdto include my entry in the lab-member list