Article version: Enterprise Server 2.14

This version of GitHub Enterprise will be discontinued on This version of GitHub Enterprise was discontinued on 2019-07-12. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise. For help with the upgrade, contact GitHub Enterprise support.

Enabling required commit signing

Protected branches are available in public repositories with GitHub Free, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server.

Repository administrators can enforce required commit signing on a branch to block all commits that are not signed and verified.

Before enabling required commit signing on a branch, you must first set the branch up as a protected branch. For more information, see "Configuring protected branches."

You can automatically enforce protected branch settings for some or all branches in your repository. For more information, see "Configuring protected branches."

  1. On GitHub Enterprise, navigate to the main page of the repository.

  2. Under your repository name, click Settings.

    Repository settings button

  3. In the left menu, click Branches.

    Repository options sub-menu

  4. Under Protected branches, select the branch you want to mark with required commit signing using the drop-down menu.

  5. Select Require signed commits.

    Require signed commits option

  6. Optionally, select Include administrators. This enforces the required signed commits on the repository administrators.

    Include administrators checkbox

  7. Click Save changes.

Ask a human

Can't find what you're looking for?

Contact us