Prevent speculative builds for repositories already publishing with non-versioned branches #2471
+119
−34
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
…on-versioned branches Add `alreadyPublishing` parameter to `Match()` to differentiate between: - Repositories onboarding to the documentation system (need speculative builds) - Repositories already publishing with non-versioned branches (don't need speculative builds) Previously, when a repository used `main` for both `git_reference_current` and `git_reference_next`, version branches (e.g., `8.15`, `9.0`) would trigger speculative builds based on product versioning. This was intended to help onboard new repositories, but inadvertently caused speculative builds for repositories already publishing to the online link registry. The `alreadyPublishing` parameter now prevents speculative builds for version branches when: - The repository uses non-versioned branches (e.g., `main`) for content sources - The repository is already publishing to the online link registry - A version branch is pushed that doesn't match any configured content source This ensures that established repositories with `main`-based workflows only build what's explicitly configured, while still allowing new repositories to use speculative builds during onboarding.
reakaleek
approved these changes
Jan 14, 2026
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.
Add
alreadyPublishingparameter toMatch()to differentiate between:Previously, when a repository used
mainfor bothgit_reference_currentandgit_reference_next, version branches (e.g.,8.15,9.0) would triggerspeculative builds based on product versioning. This was intended to help
onboard new repositories, but inadvertently caused speculative builds for
repositories already publishing to the online link registry.
The
alreadyPublishingparameter now prevents speculative builds for versionbranches when:
main) for content sourcesThis ensures that established repositories with
main-based workflows onlybuild what's explicitly configured, while still allowing new repositories to
use speculative builds during onboarding.