* New Crowdin translations by Github Action
* Reset broken translated files to English
* Ran script/i18n/homogenize-frontmatter.js
* Ran script/fix-translation-errors.js
* Reverted translated files with parsing and rendering errors
* fix malformed liquid
* add next directory to exclude list
* currentversion -> currentVersion
* fix liquid errors
* fix liquid errors
* Reset broken translated files to English
* Ran script/i18n/homogenize-frontmatter.js
* Revert /ja/github/authenticating-to-github/about-authentication-with-saml-single-sign-on
* Reset known broken translation files LAST
* Run script/i18n/homogenize-frontmatter.js
Co-authored-by: Crowdin Bot <support+bot@crowdin.com>
Co-authored-by: Rachael Sewell <rachmari@github.com>
Co-authored-by: Kevin Heis <heiskr@users.noreply.github.com>
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.
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.
885da5b3d3
