Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support a selected set of development branches #24358

Open
PaulBol opened this issue Apr 26, 2023 · 2 comments
Open

Support a selected set of development branches #24358

PaulBol opened this issue Apr 26, 2023 · 2 comments
Labels
type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@PaulBol
Copy link

PaulBol commented Apr 26, 2023

Feature Description

I'd like to set up a repository like this

  1. Branch main is protected and can only be changed through pull requests
  2. For new features developers create a branch dev-* and work with it until reviewed and merged
  3. No other branches can be created (e.g., main2, my-feature)
  4. Features branches dev-* are deleted after merging

With the implementation of #20825 items 1-3 can be achieved with (wildcard) protected branches main, dev-* and *. However, deleting the dev-* won't be possible as the branches are protected. Therefore stale feature branches would accumulate over time.

It would be great if we have the option to protected all branches except ... or to allow deleting protected branches by whitelisted users.

Screenshots

No response

@PaulBol PaulBol added type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first. labels Apr 26, 2023
@lunny
Copy link
Member

lunny commented Jun 16, 2023

Maybe we need a deletion whitelist?

@PaulBol
Copy link
Author

PaulBol commented Jun 20, 2023

For me that would be a good solution that seems consistent with whitelist approach for pushing and merging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

No branches or pull requests

2 participants