You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Regenerate post-merge CI after upstream workflow changes #144
Upstream ci.yml now runs .github/scripts/mobile-ios-preview-record.test.cjs in “Test release checks”, but the generated .github/workflows/fork-post-merge-ci.yml omits it. The drift check scripts/fork/sync-integration-ci.sh --check reports that the copy is stale, so post-merge CI skips the new test.
Regenerate the copy with scripts/fork/sync-integration-ci.sh and keep the drift check passing.
Acceptance:
The generated workflow includes the upstream test job.
Exact-head reconciliation for PR #140: independent source review, base 78f183a40d8f9682ffb0bfbf05714aa4c11ac094, head 93ba9bf83a7f1e4bd937642ba43b92738d000e68.
I confirmed the same generated-workflow drift. On that head, scripts/fork/sync-integration-ci.sh --check exits 1 because .github/workflows/fork-post-merge-ci.yml omits .github/scripts/mobile-ios-preview-record.test.cjs from “Test release checks”. That means integration-branch post-merge CI skips the upstream test; FORK.md requires regenerating the copy after an upstream ci.yml change.
The exact-head reviewer classifies this finding P2; the earlier PR review classified it P3. This is the same root cause already tracked here, so no duplicate issue is needed. Regenerate the workflow and confirm --check passes in a separate follow-up. This is not a merge hold under the P2/P3 cutoff, and no candidate files were changed.
Activity
chrisohearn commentedon Nov 18, 2026
Exact-head reconciliation for PR #140: independent source review, base
78f183a40d8f9682ffb0bfbf05714aa4c11ac094, head93ba9bf83a7f1e4bd937642ba43b92738d000e68.I confirmed the same generated-workflow drift. On that head,
scripts/fork/sync-integration-ci.sh --checkexits 1 because.github/workflows/fork-post-merge-ci.ymlomits.github/scripts/mobile-ios-preview-record.test.cjsfrom “Test release checks”. That means integration-branch post-merge CI skips the upstream test; FORK.md requires regenerating the copy after an upstreamci.ymlchange.The exact-head reviewer classifies this finding P2; the earlier PR review classified it P3. This is the same root cause already tracked here, so no duplicate issue is needed. Regenerate the workflow and confirm
--checkpasses in a separate follow-up. This is not a merge hold under the P2/P3 cutoff, and no candidate files were changed.