Repository navigation
ci(fork): auto-rebase 在閘門前先列出上游自己紅的 static 檢查 - #87
Merged
Merged
Conversation
The auto-rebase only learned that a release fails one of its own checks after its local gate went red (v1.4.242's check:test-file-runners), then re-ran the step on a clean tag and searched upstream main by hand. fork-upstream-red.mjs runs pnpm tc, upstream's pnpm lint and check:daemon-protocol-crossing on a clean worktree at the tag and writes which fail, their output, and the upstream main commits since that touch the files they name. The auto-rebase starts it beside the rebase (about a minute cold) and cherry-picks upstream's fixes before the first gate round. It is a report only: no check reads it to pass. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01C9qFZaYoGq8pJo8Qr6WVoh
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01C9qFZaYoGq8pJo8Qr6WVoh
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01C9qFZaYoGq8pJo8Qr6WVoh
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
為什麼
auto-rebase 原本要等本機閘門紅了，才知道上游 release 自己就過不了某項檢查（v1.4.242 的
check:test-file-runners），然後到乾淨的 tag 上重跑那一步、手動在上游 main 找修正。run 141 為此多跑一輪 static。改了什麼
config/scripts/fork-upstream-red.mjs <tag> <dir> <out>：在乾淨的上游 tag worktree 跑pnpm tc、上游pnpm lint（每一步）與check:daemon-protocol-crossing，寫出<out>.md／.json：哪些上游自己就紅、各自的輸出、<tag>..origin/main裡碰過那些檔的 commit（cherry-pick 候選）。fork-check-lint本來就跳過的步驟（EXCLUDED）會標出來。只是報告，不豁免任何檢查：FORK.md 明訂 fork-check 不加自動豁免，CI 仍是唯一 gate。範圍只有 static；整套單元測試、e2e 仍照原本的「CI 紅 → 重跑一次 → 乾淨 vNEW 對照」。
驗證
check:test-file-runners，候選正好是 run 141 手動找到的f34c13ca1e（test: remove 57 low-value cases and standalone browser probes stablyai/orca#33889）與ad2156c358（test: remove 140 low-value cases and 49 suites stablyai/orca#34062）；tc 與 daemon-protocol-crossing 綠。冷 worktree 全程 40 秒。EXCLUDED標記、拿掉 root 前綴去除，各自有測試變紅。make -k fork-check-static本機綠（修掉一個 type-aware finding 後）。🤖 Generated with Claude Code
https://claude.ai/code/session_01C9qFZaYoGq8pJo8Qr6WVoh