Repository navigation
Prepare jumpbox Git writes for main - #41
Merged
Merged
Conversation
This was referenced Nov 3, 2026
Member
Author
|
afaik these pipelines aren't run anywhere |
ystros
approved these changes
Nov 3, 2026
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.
The pipeline's jumpbox Git source will target
main. This is a write source, so it retains an explicit branch.Validation:
git diff --checkpassed. Parsed before/after comparisons confirm only the intended Git branch selectors changed. Localfly validate-pipeline --strictpassed.Merge the source preparation before the coordinated native branch rename. Apply the explicit
mainpipeline source only oncemainexists.Concourse Git resource contract: a read-only source can omit
branch; a source used forputneeds an explicit branch.This PR changes checked-in files only. Deployed pipeline reconfiguration and runtime checks remain operator-owned; no Concourse pipelines or jobs were modified, paused, unpaused, or triggered for this work.
Cutover plan:
Shared community configuration (draft): cloudfoundry/community#1682