Repository navigation
repos: name a branch by release month with branch_pattern - #400
Merged
Merged
Conversation
A repository that cuts one release branch per month (rel/2026-11.1)
had to have its branch: edited every month. branch_pattern with
{yyyy}|{yy}, {mm} and {n} lets the poller pick, after every fetch, the
newest matching branch of the rolled-out month: the current one from
branch_switch_day (1..28) on, the previous one before it. A month
change is an ordinary incremental branch change. No match is recorded
as last_error and the index stays; it never falls back to the default
branch. Validated at load; the pattern reaches the poller from the
file, like the index rules, so repo_state is unchanged.
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.
A repository that cuts one release branch per month needed its
branch:edited by hand every month.branch_pattern({yyyy}|{yy},{mm}, optional{n}) lets the poller pick the branch after every fetch: the newest matching month not after the target month. The target is the current month frombranch_switch_day(1..28, default 1) on, the previous month before it.repo_stateonly once its index stands, so citations never name a branch the chunks did not come from.last_errorand the index stays; never the default branch.branchorsnapshot, a pattern without year or month, a switch day without a pattern or outside 1..28.No schema change, no re-index.