Repository navigation
fix(ci): fetch enough upstream history for the fork stack check - #39
Merged
Merged
Conversation
Upstream main is now 113 commits past the fork base, so the `--depth 100` fetch no longer contains the merge base and fork-check.sh exited 1 silently under set -e. Fetch upstream main with full history but no blobs, and print a clear error when the merge base cannot be found. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Contributor
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
lukemaj
added a commit
that referenced
this pull request
Sep 27, 2026
Upstream main is now 113 commits past the fork base, so the `--depth 100` fetch no longer contains the merge base and fork-check.sh exited 1 silently under set -e. Fetch upstream main with full history but no blobs, and print a clear error when the merge base cannot be found. Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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.
Problem
The Fork Stack Model job fetches
upstream main --depth 100. Upstream pingdotgg/t3code main is now 113 commits past the fork's base (b2b43be), so the shallow fetch does not contain the merge base.git merge-base HEAD upstream/mainfails underset -eandscripts/fork-check.shexits 1 with no message. Every fork PR fails this check (e.g. #38, run 36239606669, and #37).Fix
.github/workflows/fork.yml:git fetch --filter=blob:none upstream main(full history, no blobs) instead of--depth 100.scripts/fork-check.sh: when the merge-base lookup fails, printfork-check: FAIL: cannot find the merge base with <remote>/main (fetch more history?)to stderr and exit 1.docs/fork.mddoes not mention the fetch depth, so no doc change.Proof
bash scripts/fork-check.sh --upstream upstreamends withfork-check: OK.(exit 0).git fetch upstream main --depth 100: printsfork-check: FAIL: cannot find the merge base with upstream/main (fetch more history?), exit 1. Aftergit fetch --filter=blob:none --unshallow upstream main:fork-check: OK., exit 0.Model: Claude Opus 5.5 (medium) via T3 Code
🤖 Generated with Claude Code