Repository navigation
fix(ci): track upstream commits outside the PR inventory - #332
Merged
Merged
Conversation
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.
Note
Track upstream commits missed by the PR inventory, flag empty PR merge diffs, and preserve explicit commit provenance through promotion.
What Changed
The upstream tracker now scans first-parent history from a saved SHA and retains commits missing from the PR inventory for manual review. It flags empty PR merge diffs and supports exact
Upstream-Commitprovenance through intake validation, promotion, and reconciliation.The scan position advances only with a successful issue update. History rewrites, insufficient PR inventory coverage, and an oversized retained backlog stop the run without advancing it. Existing PR rows and terminal decisions remain compatible.
Why
PR-only tracking misses changes that land outside a recorded PR merge. A read-only scan of 1,121 upstream commits found 21 without PR coverage. It also found that
pingdotgg/t3code#7892records an empty merge commit while its implementation landed separately, so selecting its merge SHA would omit the code.Validation
Checklist
Written by an agent (Codex, GPT-6).