Skip to content

Support a selected set of development branches #24358

Open
@PaulBol

Description

@PaulBol

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

Activity

added
type/featureCompletely new functionality. Can only be merged if feature freeze is not active.
type/proposalThe new feature has not been accepted yet but needs to be discussed first.
on Apr 26, 2023
lunny

lunny commented on Jun 16, 2023

@lunny
Member

Maybe we need a deletion whitelist?

PaulBol

PaulBol commented on Jun 20, 2023

@PaulBol
Author

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    type/featureCompletely new functionality. Can only be merged if feature freeze is not active.type/proposalThe new feature has not been accepted yet but needs to be discussed first.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @lunny@PaulBol

        Issue actions

          Support a selected set of development branches · Issue #24358 · go-gitea/gitea