Skip to content

Use branch protection rules #11

@Peter9192

Description

@Peter9192

Make it impossible to push directly to master/main and require at least one approving reviewer before PRs can be merged.

This helps to

  • Ensure code quality
  • Make sure others notice the changes that are made
  • Document changes to the code (with descriptive top posts, PR conversation, and by linking PRs to issues)

https://docs.github.com/en/enterprise-server@3.4/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-pull-request-reviews-before-merging

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions