Skip to content

Wildcard Protected Branch #2529

Closed
@Andlix

Description

@Andlix

With the last version, you could only protect branches that exists. But I think it should also be possible to protect branches given as wildcard (similar to GitLab),
e.g.
pu/*
release/*
*-stable
{user}/* (this branch should be protected except {user}

I think it would be a good idea to set these attitudes globally for an organization.

Activity

added
type/featureCompletely new functionality. Can only be merged if feature freeze is not active.
on Sep 17, 2017
added this to the 1.x.x milestone on Sep 17, 2017
stale

stale commented on Feb 12, 2019

@stale

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

added
issue/confirmedIssue has been reviewed and confirmed to be present or accepted to be implemented
and removed on Feb 12, 2019
mbarinc

mbarinc commented on Sep 16, 2019

@mbarinc

there are news about this feature?

lafriks

lafriks commented on Sep 18, 2019

@lafriks
Member

I'm thinking to work on this for 1.11 version

modified the milestones: 1.x.x, 1.11.0 on Sep 18, 2019
self-assigned this
on Sep 18, 2019
mbarinc

mbarinc commented on Sep 23, 2019

@mbarinc

thank you @lafriks

davidsvantesson

davidsvantesson commented on Oct 21, 2019

@davidsvantesson
Contributor

I think it would be a good idea to set these attitudes globally for an organization.

I think that should be a separate issue / pr to not make this too big. It need to consider some thing, like should it be a default branch setting that can be changed or deactivated in each repository?

With wildcard support it is possible that several settings match one branch, so the priority / combination of different branch protections need to be considered. Should only the first matching branch be used (means it must be possible to order them) or the most restrictive or the most permissive setting be used? What if there are different users/teams configured in different matching branch protection settings?

30 remaining items

Loading
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

issue/confirmedIssue has been reviewed and confirmed to be present or accepted to be implementedtype/featureCompletely new functionality. Can only be merged if feature freeze is not active.

Type

No type

Projects

No projects

Relationships

None yet

    Development

    Participants

    @lunny@davidsvantesson@techknowlogick@lafriks@mbarinc

    Issue actions

      Wildcard Protected Branch · Issue #2529 · go-gitea/gitea