e5c6dca9c5
* Add new articles * Rename article * Add secrets content * Remove permissions statements * Fix image name * Fix article name * Mention GPG verification for Codespaces in "About commit signature verification" * Add GPG verification content * Add access and security procedure * Add 💅 * Rename articles * Rename the other article * Rename again * Okay, rename this one again, too * Update link * Start access and security content * Add 💅 * Mention new functionalities in "Personalizing..." * Mention new features in "About Codespaces" * Add 💅 * Fix typos * Add audit log events * Fix so many links * Add 💅 * Add permissions * Spell access correctly, for once * Add 💅 * FIX THESE LINKS I SWEAR * Addd missing ) * Start adding procedure * update with procedural * Update content/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces.md Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com> * Update content/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.md Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com> * Apply suggestions from code review Committing all reviews ✨ Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com> Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com> Co-authored-by: Meg Bird <megbird@github.com>
1.8 KiB
title, intro, product, versions
| title | intro | product | versions | ||
|---|---|---|---|---|---|
| Managing GPG verification for Codespaces | You can allow {% data variables.product.company_short %} 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. | {% data reusables.gated-features.codespaces %} |
|
{% note %}
Note: GPG verification for {% data variables.product.prodname_codespaces %} is currently in beta and subject to change.
{% endnote %}
After you enable GPG verification, {% data variables.product.company_short %} will automatically sign commits you make in {% data variables.product.prodname_codespaces %}, and the commits will have a verified status on {% data variables.product.product_name %}. 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 {% data variables.product.product_name %}-signed commits, see "About commit signature verification."
{% data reusables.user_settings.access_settings %} {% data reusables.user_settings.codespaces-tab %}
- Under "GPG verification", select the setting you want for GPG verification.
- 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.
