Repository navigation
Set BBR and OpenStack CPI default branches to main - #1681
Merged
Merged
Conversation
Record main for bosh-backup-and-restore and bosh-openstack-cpi-release.
This was referenced Nov 3, 2026
aramprice
marked this pull request as ready for review
November 3, 2026 01:41
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.
Both repositories now default to protected main. OpenStack CPI's native rename and BBR's manual rename were verified with preserved refs/tags, prior protection policies, workflow/integration state and fresh-clone defaults. Tracking issues are closed for the GitHub cutovers.
Concourse pipelines were not paused, resumed or modified by the agent, and no checks/builds or one-off probes were triggered. Current instructions keep runtime coordination/reconfiguration operator-owned.
Validation of this PR: generated configuration changes only the two defaults and protection selectors; other generated configuration is unchanged.
Peribolos synchronization is asynchronous. No individual run is a checklist gate; an eventual successful synchronization containing the merged configuration remains required before org configuration is fully applied.