Managing GPG verification for Codespaces

You can allow GitHub to automatically use GPG to sign commits you make in your codespaces, so other people can be confident that the changes come from a trusted source.

Codespaces is available for organizations using GitHub Team or GitHub Enterprise Cloud. For more information, see "GitHub's products."

After you enable GPG verification, GitHub will automatically sign commits you make in Codespaces, and the commits will have a verified status on GitHub. By default, GPG verification is disabled for codespaces you create. You can choose to allow GPG verification for all repositories or specific repositories. Only enable GPG verification for repositories that you trust. For more information about GitHub-signed commits, see "About commit signature verification."

Once you enable GPG verification, it will immediately take effect for all your codespaces.

  1. In the upper-right corner of any page, click your profile photo, then click Settings. Settings icon in the user bar
  2. In the left sidebar, click Codespaces. Codespaces tab in the user settings sidebar
  3. Under "GPG verification", select the setting you want for GPG verification. Radio buttons to manage GPG verification
  4. If you chose "Selected repositories", select the drop-down menu, then click a repository you want enable GPG verification for. Repeat for all repositories you want to enable GPG verification for. "Selected repositories" drop-down menu

Note: Once you have enabled GPG verification for Codespaces, you also must append -s to each commit in order for it to be signed. To do this in Visual Studio Code, ensure the "Git: Enable Commit Signing" option is enabled from the Settings.

Did this doc help you?Privacy policy

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

Or, learn how to contribute.