Repository navigation
Conversation
This was referenced Nov 3, 2026
Member
Author
|
Feel free to merge and reconfigure at any time. Since this is a read-only resource the default branch will be used, regardless of name. |
Member
Author
|
PSA: the |
Member
Author
|
bosh-deployment default branch has been cut over from |
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.
Remove the explicit
masterselector from read-onlybosh-deploymentGit sources, allowing them to follow the repository default before and after its rename. These changes can be merged and applied while the default is stillmaster.Concourse Git resource contract: a read-only source can follow the default by omitting
branch; a write source requires an explicit branch.Validation:
git diff --checkpassed. Exact parsed before/after comparison confirms only the intended Git source branch selectors changed. Modern strict offline pipeline validation reports the same existing template/legacy-schema errors before and after; runtime compatibility requires operator verification.Only checked-in definitions are changed. Deployed pipeline reconfiguration and runtime checks remain operator-owned. No Concourse pause/unpause, configuration, cache clearing, resource checks, job triggers or configure-script execution were performed.
Cutover steps, consumer readiness and rollback: cloudfoundry/bosh-deployment#539
Community configuration (draft): cloudfoundry/community#1686