feat(forks): track ledoent/sentry@master in org fork-sync inventory - #4
Merged
Conversation
The fork-sync-and-digest org workflow already merge-upstream's all forks listed in forks.yml. Add ledoent/sentry so its master gets the same daily FF from getsentry/sentry. Without this, master sits frozen at fork-creation time and every PR from a *-kencove rebase branch shows false conflicts against an obsolete base. ledoent/seer's upstream (getsentry/seer) is private — the merge-upstream API call would 404 with our PAT. Documented as a commented-out entry so the next person looking knows we considered it; actual sync stays manual via the feature/explorer-endpoints rebase pattern.
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
1 participant
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.
What changed
Adds
ledoent/sentryto.github/forks.ymlso the existingfork-sync-and-digestorg workflow merge-upstream's itsmasterbranch daily fromgetsentry/sentry@master.Why
Without auto-sync, our fork's
masterstays frozen at fork-creation time (Feb 2026 =26.2.0). Every PR opened from a*-kencoverebase branch (e.g. the in-progress 26.5.0 rebase at ledoent/sentry#2) shows GitHub's "this branch has conflicts" against the obsolete master — false signal that wastes review attention.Current drift: ledoent/sentry@master is 166 commits behind upstream. First workflow run after merge will catch us up.
Entry shape
upstream_org: nullskips the daily [MIG] PR scan (that's an OCA-specific convention). The merge-upstream API just needs the fork's branch name; it implicitly targets the parent repo's same-named branch.ledoent/seer commented out
getsentry/seeris private. Themerge-upstreamAPI call needs read access to the upstream repo and would 404 with our PAT. Documented as a commented entry so the next reader knows we considered it; sync stays manual via thefeature/explorer-endpointsrebase pattern.Rollback
git revert— sync stops; nothing else affected. The 166-commit gap continues to grow until someone manually FF's master.