Add handling for speculative matches in content source logic #1297
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
This will flag version branches as a speculative match ensuring we'll onboard new version branches before they are actively marked as current / next. If a current branch is already a version branch we will only build new version branches speculatively. This also ensures new repositories will speculatively build for `main` / `master` or version branches.
reakaleek
approved these changes
May 21, 2025
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.
This will flag version branches as a speculative match ensuring we'll onboard new version branches before they are actively marked as current / next.
If a current branch is already a version branch we will only build new version branches speculatively.
This also ensures new repositories will speculatively build for
main/masteror version branches.This allows repositories to
current(e.g 9.1) branch.links.jsonfrom9.1.assembler.ymlto 9.1 now at anytime because alinks.jsonwill have been published for it.Otherwise we can never pull an update to
assembler.ymlbecause that would break the link resolvers trying to find thelinks.jsonfor thecurrentbranch.This also ensures new repositories can onboard their
mainandmasterbranches without touchingassembler.yml.