Exclude a repo from configuration management #210
Merged
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 adds the ability to exclude a (core) repo from configuration management, and uses that ability to exclude opensafely-core/ethelred. Why? Team PIN have been experimenting with trunk-based development as well as GitHub flow workflows, and have decided to adopt a workflow that sits between the two: [Ship / Show / Ask][1]. To adopt this workflow, they would like to allow PRs to be merged to the mainline branch without approval; and *possibly* to remove branch protection rules from the mainline branch. [1]: https://martinfowler.com/articles/ship-show-ask.html
bloodearnest
approved these changes
Sep 18, 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 adds the ability to exclude a (core) repo from configuration management, and uses that ability to exclude opensafely-core/ethelred.
Why?
Team PIN have been experimenting with trunk-based development as well as GitHub flow workflows, and have decided to adopt a workflow that sits between the two: Ship / Show / Ask. To adopt this workflow, they would like to allow PRs to be merged to the mainline branch without approval; and possibly to remove branch protection rules from the mainline branch.