Skip to content
Rulesets/Branch Protection - DefaultActive
NameBranch Protection - Default
Enforcement statusActive - This ruleset will be enforced

Target branches

Branch targeting criteria

  • Default

Rules

Which rules should be applied?

Branch rules

Restrict deletionsOnly allow users with bypass permissions to delete matching refs.
Require linear historyPrevent merge commits from being pushed to matching refs.
Require a pull request before mergingRequire all commits be made to a non-target branch and submitted via a pull request before they can be merged.
Block force pushesPrevent users with push access from force pushing to refs.
Require workflows to pass before mergingRequire all changes made to a targeted branch to pass the specified workflows before they can be merged.
  • Do not require workflows on creationAllow repositories and branches to be created if a check would otherwise prohibit it.
  • Workflow configurations

    No workflow configurations found

Require code scanning resultsChoose which tools must provide code scanning results before the reference is updated. When configured, code scanning must be enabled and have results for both the commit and the reference being updated.
  • Required tools and alert thresholds
    • CodeQL
      Security alerts threshold:
      High or higher
      Alerts threshold:
      Errors
    Tools that must provide code scanning results for this rule to pass. Learn more about enabling code scanning.
Automatically request Copilot code reviewRequest Copilot code review for new pull requests automatically if the author has access to Copilot code review and their premium requests quota has not reached the limit.

Restrictions

No restrictions have been added