Signed commits from the GitLab UI

Tier: Free, Premium, Ultimate Offering: Self-managed, GitLab Dedicated
History
  • Introduced in GitLab 15.4.
  • Displaying Verified badge for signed GitLab UI commits introduced in GitLab 16.3 with a flag named gitaly_gpg_signing. Disabled by default.
  • Verifying the signatures using multiple keys specified in rotated_signing_keys option introduced in GitLab 16.3.
  • Enabled by default on self-managed and GitLab Dedicated in GitLab 17.0.
The availability of this feature is controlled by a feature flag. For more information, see the history. This feature is available for testing, but not ready for production use.

When you create a commit using the GitLab user interface, the commit is not pushed directly by you. Instead, the commit is created on your behalf.

To sign these commits, GitLab uses a global key configured for the instance. Because GitLab doesn’t have access to your private key, the created commit can’t be signed by using the key associated with your account.

For example, if User A applies suggestions authored by User B, the commit contains the following: 

Author: User A <a@example.com>
Committer: GitLab <noreply@gitlab.com>

Co-authored-by: User B <b@example.com>

Prerequisites

Before you can use commit signing for GitLab UI commits, you must configure it.

Committer field of the commits

By default, when a commit is created on GitLab, the Author of the commit is set as the Committer of the commit. To avoid confusion, when the commit is signed, the signature should belong to the Committer of the commit.

This is why you should configure the Committer field to point to the instance itself. For example, when this feature becomes enabled on GitLab.com, the Committer field is: GitLab <noreply@gitlab.com>.

GitLab provides multiple security features that rely on the Committer field to be set to the user who creates the commit. For example:

When a commit is signed by the instance, GitLab relies on the Author field for those features.

Commits created using REST API

Commits created using the REST API. are also considered as web-based commits. Using the REST API endpoint, you can set author_name and author_email fields of the commit, which makes it possible to create commits on behalf of other users.

When commit signing is enabled, commits created using the REST API that have different author_name and author_email than the user who sends the API request are rejected.

Rebasing from UI

When signing commits made in the UI is enabled and you rebase a merge request from the UI, the commits aren’t signed.

In this case, new commits aren’t created. The merge request commits are modified and added on top of the target branch, so GitLab cannot sign them.

To have rebased commits signed, a workaround is to rebase locally and push the changes to the merge request branch.