Skip to content

Missing elements in branch protection rules #773

@fardarter

Description

@fardarter

See 15 under https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule

- Select Restrict who can push to matching branches.
  - Optionally, to also restrict the creation of matching branches, select Restrict pushes that create matching branches.

Is there a reason this config isn't supported in branch protection rules? Is it just that nobody has worked on it or is there a philosophy being applied?

I have a small team, and would like only allow maintainers to merge code. Is there some other mechanism for that? I would prefer not to use codeowners for this due to the notifications being incredibly noisy.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Staleneeds triageIssues that require review from maintainers

    Type

    No type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions