docs(flaky-tests): document fork PR uploads per-repo opt-in#33
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
|
Verification status (2026-05-19): Eng PR not merged. Hold.
Hold until analytics-cli#1086 and trunk#31970 merge. Note: PR #35 also documents this feature with a slightly different scope. Coordinate which docs PR to merge. Label: |
|
Verification status (2026-05-29): Eng PR not merged. Hold.
Progress since last sweep: the monolith half (trunk#31970) shipped. Remaining blocker is the CLI half (analytics-cli#1101). Hold until #1101 merges and ships in a released CLI version. Note: PR #35 also documents this feature with a slightly different scope. Coordinate which docs PR to merge. Label: |
Adds a new "Uploading from Fork Pull Requests" section to the multiple-repositories page explaining how to enable the settings toggle, copy the public repo identifier, and configure fork PR workflows to upload test results without exposing the org API token. Source: trunk-io/trunk2#3908 Co-Authored-By: Claude <noreply@anthropic.com>
34bfb2d to
4fd456a
Compare
|
Verification status (May 30, 2026): Verified: customers can use this. Ready to publish.
Prior verdict was Generated by Claude Code |
|
Verification status (May 31, 2026): The blocking analytics-cli dependency has merged; fork PR upload docs (per-repo flow) are clear to ship.
Next action: merge this PR. Generated by Claude Code |
|
Docs Verify Sweep · June 1, 2026 · ✅ live Feature is live in production. Ready to merge. Unchanged from previous sweep (May 31, 2026). Generated by Claude Code |
…rotation Merges #35's fuller content into the section #33 added to main, leaving one fork-PR section instead of two overlapping ones. Adds the why (fork pull_request workflows run read-only and can't read secrets), the public vs private guidance, and a raw-CLI alternative (--public-repo-id / TRUNK_PUBLIC_REPO_ID, sent on the X-Trunk-Public-Repo-Id header). Fixes the rotation claim: the prior <Warning> said re-enabling mints a new identifier and invalidates the old one. Source (frontend fork-pr-uploads.ts upsert) only generates publicRepoIdentifier on row create; the enable/disable update never touches it, so the identifier persists and is reused on re-enable. Verified the action input (analytics-uploader action.yaml: public-repo-id) and CLI flag (analytics-cli upload_command.rs: public_repo_id) both exist. Drops #### subheadings for bold-lead paragraphs to keep the page at h3. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…rotation (#35) Merges #35's fuller content into the section #33 added to main, leaving one fork-PR section instead of two overlapping ones. Adds the why (fork pull_request workflows run read-only and can't read secrets), the public vs private guidance, and a raw-CLI alternative (--public-repo-id / TRUNK_PUBLIC_REPO_ID, sent on the X-Trunk-Public-Repo-Id header). Fixes the rotation claim: the prior <Warning> said re-enabling mints a new identifier and invalidates the old one. Source (frontend fork-pr-uploads.ts upsert) only generates publicRepoIdentifier on row create; the enable/disable update never touches it, so the identifier persists and is reused on re-enable. Verified the action input (analytics-uploader action.yaml: public-repo-id) and CLI flag (analytics-cli upload_command.rs: public_repo_id) both exist. Drops #### subheadings for bold-lead paragraphs to keep the page at h3. Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Summary
flaky-tests/get-started/multiple-repositories.mdxpublic-repo-idinstead of the org API tokenSource
Test plan
Generated by Claude Code