Managing a branch protection rule

You can create a branch protection rule to enforce certain workflows for one or more branches, such as requiring an approving review or passing status checks for all pull requests merged into the protected branch.

People with admin permissions to a repository can manage branch protection rules.

Las ramas protegidas están disponibles en los repositorios públicos con GitHub Free y GitHub Free para las organizaciones, y en los repositorios públicos y privados con GitHub Pro, GitHub Team, Nube de GitHub Enterprise, y GitHub Enterprise Server. Para obtener más información, consulta la sección "Productos de GitHub".

About branch protection rules

Puedes crear una regla de protección de rama en un repositorio para la rama específica, todas las ramas, o cualquier rama que coincida con un patrón de nombre que especifiques con la sintaxis fnmatch. Por ejemplo, para proteger cualquier rama que contenga la palabra release, puedes crear una regla de rama de *release*.

You can create a rule for all current and future branches in your repository with the wildcard syntax *. Because GitHub uses the File::FNM_PATHNAME flag for the File.fnmatch syntax, the wildcard does not match directory separators (/). For example, qa/* will match all branches beginning with qa/ and containing a single slash. You can include multiple slashes with qa/**/*, and you can extend the qa string with qa**/**/* to make the rule more inclusive. For more information about syntax options for branch rules, see the fnmatch documentation.

If a repository has multiple protected branch rules that affect the same branches, the rules that include a specific branch name have the highest priority. If there is more than one protected branch rule that references the same specific branch name, then the branch rule created first will have higher priority.

Protected branch rules that mention a special character, such as *, ?, or ], are applied in the order they were created, so older rules with these characters have a higher priority.

To create an exception to an existing branch rule, you can create a new branch protection rule that is higher priority, such as a branch rule for a specific branch name.

For more information about each of the available branch protection settings, see "About protected branches."

Creating a branch protection rule

When you create a branch rule, the branch you specify doesn't have to exist yet in the repository.

  1. En GitHub.com, visita la página principal del repositorio.

  2. Debajo de tu nombre de repositorio, da clic en Configuración. Botón de configuración del repositorio

  3. En el menú izquierdo, da clic en Ramas. Sub-menú de opciones de repositorio

  4. Junto a "Reglas de protección de rama", da clic en Agregar regla. Botón de agregar regla de protección de rama

  5. Debajo del "Patrón del nombre de la rama", teclea el nombre de la rama o el patrón que quieras proteger. Campo de regla de rama

  6. Optionally, enable required pull requests.

    • Under "Protect matching branches", select Require a pull request before merging. Pull request review restriction checkbox

    • Optionally, to require approvals before a pull request can be merged, select Require approvals, click the Required number of approvals before merging drop-down menu, then select the number of approving reviews you would like to require on the branch. Drop-down menu to select number of required review approvals

    • Optionally, to dismiss a pull request approval review when a code-modifying commit is pushed to the branch, select Dismiss stale pull request approvals when new commits are pushed. Dismiss stale pull request approvals when new commits are pushed checkbox

    • Optionally, to require review from a code owner when the pull request affects code that has a designated owner, select Require review from Code Owners. For more information, see "About code owners." Require review from code owners

    • Optionally, to allow specific people or teams to push code to the branch without being subject to the pull request rules above, select Allow specific actors to bypass pull request requirements. Then, search for and select the people or teams who are allowed to bypass the pull request requirements. Allow specific actors to bypass pull request requirements checkbox

    • Optionally, if the repository is part of an organization, select Restrict who can dismiss pull request reviews. Then, search for and select the people or teams who are allowed to dismiss pull request reviews. For more information, see "Dismissing a pull request review." Restrict who can dismiss pull request reviews checkbox

  7. Optionally, enable required status checks. For more information, see "About status checks."

    • Select Require status checks to pass before merging. Required status checks option
    • Optionally, to ensure that pull requests are tested with the latest code on the protected branch, select Require branches to be up to date before merging. Loose or strict required status checkbox
    • Search for status checks, selecting the checks you want to require. Search interface for available status checks, with list of required checks
  8. Optionally, select Require conversation resolution before merging. Require conversation resolution before merging option

  9. Optionally, select Require signed commits. Require signed commits option

  10. Optionally, select Require linear history. Required linear history option

  11. Optionally, to merge pull requests using a merge queue, select Require merge queue. For more information about merge queues, see "Using a merge queue." Require merge queue option

    Tip: The pull request merge queue feature is currently in limited public beta and subject to change. Organizations owners can request early access to the beta by joining the waitlist.

  12. Optionally, select Include administrators. Include administrators checkbox

  13. Optionally, if your repository is owned by an organization using GitHub Team or Nube de GitHub Enterprise, enable branch restrictions.

    • Select Restrict who can push to matching branches. Branch restriction checkbox
    • Search for and select the people, teams, or apps who will have permission to push to the protected branch. Branch restriction search
  14. Optionally, under "Rules applied to everyone including administrators", select Allow force pushes. For more information about force pushes, see "Allow force pushes." Allow force pushes option

  15. Optionally, select Allow deletions. Allow branch deletions option

  16. Click Create.

Editing a branch protection rule

  1. En GitHub.com, visita la página principal del repositorio.
  2. Debajo de tu nombre de repositorio, da clic en Configuración. Botón de configuración del repositorio
  3. En el menú izquierdo, da clic en Ramas. Sub-menú de opciones de repositorio
  4. To the right of the branch protection rule you want to edit, click Edit. Edit button
  5. Make your desired changes to the branch protection rule.
  6. Click Save changes. Save changes button

Deleting a branch protection rule

  1. En GitHub.com, visita la página principal del repositorio.
  2. Debajo de tu nombre de repositorio, da clic en Configuración. Botón de configuración del repositorio
  3. En el menú izquierdo, da clic en Ramas. Sub-menú de opciones de repositorio
  4. To the right of the branch protection rule you want to delete, click Delete. Delete button

¿Te ayudó este documento?

Política de privacidad

¡Ayúdanos a hacer geniales estos documentos!

Todos los documentos de GitHub son de código abierto. ¿Notas algo que esté mal o que no sea claro? Emite una solicitud de cambios.

Haz una contribución

O, aprende cómo contribuir.