feat(forks): preemptively track 20.0 so sync auto-activates - #3
Merged
Conversation
Adds "20.0" to the branches list on every OCA fork (18 of them). 20.0 doesn't exist anywhere yet — neither on OCA upstream nor on any ledoent fork — so today every sync attempt returns HTTP 404 "Branch not found" and lands in the "skipped (branch n/a)" bucket per the existing skip-on-404 logic. The moment OCA cuts 20.0 on a given repo, the next daily run picks up that branch with zero config edits. No flag day, no missed-update window between "OCA cuts 20.0" and "we notice and add it to forks.yml". Cost: the daily digest's "skipped" count grows by ~18 until 20.0 starts existing on upstream. Skipped entries don't appear in failure counts or in the email subject, so the cosmetic impact is one number in the one-line summary. OpenUpgrade gets ["19.0", "20.0"] (not the [overlay, 19.0] from before): same rationale, the `ledoent` overlay branch isn't an upstream mirror and shouldn't be merged into.
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
Adds `"20.0"` to the `branches:` list on every OCA fork (18 entries). 20.0 doesn't exist anywhere yet — neither on OCA upstream nor on any ledoent fork — so today every sync attempt against 20.0 returns `HTTP 404 Branch not found` and lands in the "skipped (branch n/a)" bucket per the existing skip-on-404 logic introduced in #2.
Why
When OCA cuts the 20.0 branch on each repo (likely Oct 2026 with Odoo 20.0 GA), the next daily run picks up the new branch with zero config edits. No flag day, no missed-update window between "OCA cuts 20.0" and "we notice and add it to forks.yml".
Cost
The daily digest's "skipped" count grows by ~18 entries until 20.0 starts existing on upstream. Skipped entries:
So cosmetic impact is one number in the summary line. No noise in failures, no per-fork list rendered for skipped entries.
Coverage
Tests pass (19/19). Safe squash-merge.