For more information, see " About rule layering." Unlike protection rules, multiple rulesets can apply at the same time, so you can be confident that every rule targeting a branch or tag in your repository will be evaluated when someone interacts with that branch or tag.Rulesets have the following advantages over branch and tag protection rules. For more information, see " Configuring tag protection rules." This will implement the same tag protections you currently have in place for your repository. Many of the rules you can define in rulesets are similar to protection rules, and you can start using rulesets without overriding any of your existing protection rules.Īdditionally, you can import existing tag protection rules into repository rulesets. Rulesets work alongside any branch protection rules and tag protection rules in a repository. ![]() About rulesets, protected branches, and protected tags There is a limit of 75 rulesets per repository, and 75 organization-wide rulesets. This can be users with a certain role, such as repository administrator, or it can be specific teams or GitHub Apps. When you create a ruleset, you can allow certain users to bypass the rules in the ruleset. For more information on fnmatch syntax, see " Creating rulesets for a repository." For example, you could use the pattern releases/**/* to target all branches in your repository whose name starts with the string releases/. You can use fnmatch syntax to define a pattern to target specific branches, tags, and repositories. For example, you could set up a ruleset for your repository's feature branch that requires signed commits and blocks force pushes for all users except repository administrators.įor each ruleset you create, you specify which branches or tags in your repository, or which repositories in your organization, the ruleset applies to. You can control things like who can push commits to a certain branch and how the commits must be formatted, or who can delete or rename a tag. ![]() You can create rulesets to control how people can interact with selected branches and tags in a repository. A ruleset is a named list of rules that applies to a repository, or to multiple repositories in an organization.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |