![]() ![]() The rules from each source are aggregated, and all rules apply. An existing branch protection rule for the my-feature branch requires a linear commit history, and two reviews on pull requests before they can be merged.This ruleset requires signed commits, and three reviews on pull requests before they can be merged. An administrator of the repository has set up a ruleset targeting the my-feature branch.As well as layering with each other, rulesets also layer with protection rules targeting the same branch or tag.įor example, consider the following situation for the my-feature branch of the octo-org/octo-repo repository. If the same rule is defined in different ways across the aggregated rulesets, the most restrictive version of the rule applies. Instead, if multiple rulesets target the same branch or tag in a repository, the rules in each of these rulesets are aggregated. For more information, see " Managing rulesets for a repository" in the GitHub Enterprise Cloud documentation.Ī ruleset does not have a priority. Use an "Evaluate" status to test a ruleset before making it active, and use an insights page to view which user actions are being affected by rules.For more information, see " Available rules for rulesets" in the GitHub Enterprise Cloud documentation. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |