add topic frontmatter to articles (#18245)
This commit is contained in:
Rachael Sewell
@@ -5,9 +5,10 @@ redirect_from:
|
||||
- /github/administering-a-repository/about-dependabot
|
||||
- /github/administering-a-repository/about-github-dependabot
|
||||
- /github/administering-a-repository/about-github-dependabot-version-updates
|
||||
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
{% data reusables.dependabot.beta-note %}
|
||||
|
||||
@@ -11,6 +11,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
{% data reusables.notifications.outbound_email_tip %}
|
||||
|
||||
@@ -7,6 +7,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
{% data reusables.pull_requests.configure_pull_request_merges_intro %} You can enforce one type of merge method, such as commit squashing or rebasing, by only enabling the desired method for your repository.
|
||||
|
||||
@@ -19,6 +19,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
### About branch protection rules
|
||||
|
||||
@@ -11,6 +11,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
### About releases
|
||||
|
||||
@@ -10,6 +10,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=3.0'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
{% data reusables.secret-scanning.beta %}
|
||||
|
||||
@@ -5,6 +5,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=3.0'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
### Setting up your repository securely
|
||||
|
||||
@@ -7,6 +7,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
Query parameters are optional parts of a URL you can customize to share a specific web page view, such as search filter results, an issue template, or the release form page on {% data variables.product.prodname_dotcom %}. To create your own query parameters, you must match the key and value pair.
|
||||
|
||||
@@ -9,6 +9,8 @@ versions:
|
||||
redirect_from:
|
||||
- /github/administering-a-repository/setting-the-default-branch
|
||||
- /articles/setting-the-default-branch
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
### About changing the default branch
|
||||
|
||||
@@ -8,6 +8,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
### About topics
|
||||
|
||||
@@ -6,6 +6,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=2.21'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
|
||||
@@ -5,6 +5,8 @@ permissions: 'People with write permissions to a repository can configure {% dat
|
||||
miniTocMaxHeadingLevel: 4
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
{% data reusables.dependabot.beta-note %}
|
||||
|
||||
@@ -8,6 +8,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
Anyone with admin permissions to a repository can configure autolink references to link issues, pull requests,{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %} commit messages, and release descriptions{% else %} and commit messages{% endif %} to external third-party services.
|
||||
|
||||
@@ -7,6 +7,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
{% data reusables.pull_requests.configure_pull_request_merges_intro %}
|
||||
|
||||
@@ -7,6 +7,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
{% data reusables.pull_requests.configure_pull_request_merges_intro %}
|
||||
|
||||
@@ -8,5 +8,7 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
|
||||
@@ -9,6 +9,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=3.0'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
{% data reusables.secret-scanning.beta %}
|
||||
|
||||
@@ -5,6 +5,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=2.23'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
{% data reusables.actions.about-artifact-log-retention %}
|
||||
|
||||
@@ -4,6 +4,8 @@ intro: 'You can customize how {% data variables.product.prodname_dependabot %} m
|
||||
permissions: 'People with write permissions to a repository can configure {% data variables.product.prodname_dependabot %} for the repository.'
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
{% data reusables.dependabot.beta-note %}
|
||||
|
||||
@@ -7,6 +7,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
Use a *.gitattributes* file to mark files that match a given "pattern" with the specified attributes. A *.gitattributes* file uses the same rules for matching as _.gitignore_ files. For more information, see [PATTERN FORMAT](https://www.git-scm.com/docs/gitignore#_pattern_format) in the Git documentation.
|
||||
|
||||
|
||||
@@ -7,6 +7,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
Until you add an image, repository links expand to show basic information about the repository and the owner's avatar. Adding an image to your repository can help identify your project across various social platforms.
|
||||
|
||||
@@ -11,5 +11,7 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
|
||||
@@ -9,6 +9,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
{% data reusables.organizations.owners-and-admins-can %} delete an organization repository. If **Allow members to delete or transfer repositories for this organization** has been disabled, only organization owners can delete organization repositories. {% data reusables.organizations.new-repo-permissions-more-info %}
|
||||
|
||||
@@ -10,6 +10,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
### Deleting a branch used for a pull request
|
||||
|
||||
@@ -5,6 +5,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=2.22'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
|
||||
@@ -6,6 +6,8 @@ redirect_from:
|
||||
- /articles/displaying-a-sponsor-button-in-your-repository
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
### About FUNDING files
|
||||
|
||||
@@ -4,6 +4,8 @@ intro: 'You can configure your repository so that {% data variables.product.prod
|
||||
permissions: 'People with write permissions to a repository can enable or disable {% data variables.product.prodname_dependabot_version_updates %} for the repository.'
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
{% data reusables.dependabot.beta-note-no-link %}
|
||||
|
||||
@@ -5,6 +5,8 @@ product: '{% data reusables.gated-features.discussions %}'
|
||||
permissions: People with admin permissions to a repository can enable discussions for the repository.
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
{% data reusables.discussions.beta %}
|
||||
|
||||
@@ -6,6 +6,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
|
||||
|
||||
@@ -5,6 +5,8 @@ redirect_from:
|
||||
- /github/administering-a-repository/keeping-your-actions-up-to-date-with-github-dependabot
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
{% data reusables.dependabot.beta-note %}
|
||||
|
||||
@@ -4,5 +4,7 @@ intro: '{% data variables.product.prodname_dependabot %} can maintain your repos
|
||||
mapTopic: true
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
|
||||
@@ -7,6 +7,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
|
||||
@@ -3,6 +3,8 @@ title: Listing dependencies configured for version updates
|
||||
intro: 'You can view the dependencies that {% data variables.product.prodname_dependabot %} monitors for updates.'
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
{% data reusables.dependabot.beta-note %}
|
||||
|
||||
@@ -21,6 +21,8 @@ versions:
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
permissions: People with admin permissions to a repository can manage branch protection rules.
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
### About branch protection rules
|
||||
|
||||
@@ -6,6 +6,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=3.0'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
{% data reusables.secret-scanning.beta %}
|
||||
|
||||
@@ -1,12 +1,14 @@
|
||||
---
|
||||
title: Managing auto-merge for pull requests in your repository
|
||||
intro: "You can allow or disallow auto-merge for pull requests in your repository."
|
||||
intro: You can allow or disallow auto-merge for pull requests in your repository.
|
||||
product: '{% data reusables.gated-features.auto-merge %}'
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=3.1'
|
||||
github-ae: '*'
|
||||
permissions: People with maintainer permissions can manage auto-merge for pull requests in a repository.
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
If you allow auto-merge for pull requests in your repository, people can configure individual pull requests in the repository to merge automatically when all merge requirements are met. For more information, see "[Automatically merging a pull request](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)."
|
||||
|
||||
@@ -8,5 +8,7 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
|
||||
@@ -7,6 +7,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>3.0'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
### About {% data variables.large_files.product_name_short %} objects in archives
|
||||
|
||||
@@ -3,6 +3,8 @@ title: Managing pull requests for dependency updates
|
||||
intro: 'You manage pull requests raised by {% data variables.product.prodname_dependabot %} in much the same way as other pull requests, but there are some extra options.'
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
{% data reusables.dependabot.beta-note %}
|
||||
|
||||
@@ -13,6 +13,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion ver_gt "github-ae@latest" %}
|
||||
|
||||
@@ -8,5 +8,7 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
|
||||
@@ -11,6 +11,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=3.0'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
|
||||
@@ -6,6 +6,8 @@ redirect_from:
|
||||
- /github/administering-a-repository/managing-people-and-teams-with-access-to-your-repository
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
### About managing access to your repository
|
||||
|
||||
@@ -7,6 +7,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
Anyone with admin permissions to a repository can enable or disable the automatic deletion of branches.
|
||||
|
||||
@@ -9,6 +9,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
An organization owner must allow forks of private{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} and internal{% endif %} repositories on the organization level before you can allow or disallow forks for a specific repository. For more information, see "[Managing the forking policy for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization)."
|
||||
|
||||
@@ -9,5 +9,7 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
|
||||
@@ -5,6 +5,8 @@ permissions: People with write permissions to a repository can rename a branch i
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=3.1'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
### About renaming branches
|
||||
|
||||
@@ -7,6 +7,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
When you rename a repository, all existing information, with the exception of project site URLs, is automatically redirected to the new name, including:
|
||||
|
||||
|
||||
@@ -5,6 +5,8 @@ redirect_from:
|
||||
- /articles/restoring-a-deleted-repository
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
Anyone can restore deleted repositories that were owned by their own user account. Organization owners can restore deleted repositories that were owned by the organization.
|
||||
|
||||
@@ -8,5 +8,7 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=3.0'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
|
||||
@@ -10,6 +10,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
### About repository visibility changes
|
||||
|
||||
@@ -16,6 +16,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
### About repository transfers
|
||||
|
||||
@@ -1,11 +1,13 @@
|
||||
---
|
||||
title: Troubleshooting required status checks
|
||||
intro: 'You can check for common errors and resolve issues with required status checks.'
|
||||
intro: You can check for common errors and resolve issues with required status checks.
|
||||
product: '{% data reusables.gated-features.protected-branches %}'
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
If you have a check and a status with the same name, and you select that name as a required status check, both the check and the status are required. For more information, see "[Checks](/rest/reference/checks)."
|
||||
|
||||
@@ -7,6 +7,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.navigate-to-branches %}
|
||||
|
||||
@@ -7,6 +7,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
{% note %}
|
||||
|
||||
@@ -9,6 +9,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
|
||||
|
||||
@@ -6,6 +6,9 @@ redirect_from:
|
||||
- /articles/about-anonymized-image-urls
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- identity
|
||||
- access management
|
||||
---
|
||||
|
||||
To host your images, {% data variables.product.product_name %} uses the [open-source project Camo](https://github.com/atmos/camo). Camo generates an anonymous URL proxy for each image which hides your browser details and related information from other users. The URL starts `https://<subdomain>.githubusercontent.com/`, with different subdomains depending on how you uploaded the image.
|
||||
|
||||
@@ -5,6 +5,9 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- identity
|
||||
- access management
|
||||
---
|
||||
|
||||
### About authentication to {% data variables.product.prodname_dotcom %}
|
||||
|
||||
@@ -7,6 +7,8 @@ redirect_from:
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- sso
|
||||
---
|
||||
|
||||
### About authentication with SAML SSO
|
||||
|
||||
@@ -9,6 +9,9 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- identity
|
||||
- access management
|
||||
---
|
||||
|
||||
### About commit signature verification
|
||||
|
||||
@@ -10,6 +10,9 @@ redirect_from:
|
||||
- /articles/about-githubs-ip-addresses
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- identity
|
||||
- access management
|
||||
---
|
||||
You can retrieve a list of {% data variables.product.prodname_dotcom %}'s IP addresses from the [meta](https://api.github.com/meta) API endpoint. For more information, see "[Meta](/rest/reference/meta)."
|
||||
|
||||
|
||||
@@ -7,6 +7,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- ssh
|
||||
---
|
||||
|
||||
When you set up SSH, you'll [generate an SSH key and add it to the ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) and then [add the key to your {% data variables.product.product_name %} account](/articles/adding-a-new-ssh-key-to-your-github-account). Adding the SSH key to the ssh-agent ensures that your SSH key has an extra layer of security through the use of a passphrase. For more information, see "[Working with SSH key passphrases](/articles/working-with-ssh-key-passphrases)."
|
||||
|
||||
@@ -6,6 +6,8 @@ redirect_from:
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
topics:
|
||||
- 2fa
|
||||
---
|
||||
|
||||
For {% data variables.product.product_name %}, the second form of authentication is a code that's generated by an application on your mobile device{% if currentVersion == "free-pro-team@latest" %} or sent as a text message (SMS){% endif %}. After you enable 2FA, {% data variables.product.product_name %} generates an authentication code any time someone attempts to sign into your {% data variables.product.product_name %} account. The only way someone can sign into your account is if they know both your password and have access to the authentication code on your phone.
|
||||
|
||||
@@ -9,6 +9,8 @@ redirect_from:
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
topics:
|
||||
- 2fa
|
||||
---
|
||||
|
||||
With two-factor authentication enabled, you'll need to provide an authentication code when accessing {% data variables.product.product_name %} through your browser. If you access {% data variables.product.product_name %} using other methods, such as the API or the command line, you'll need to use an alternative form of authentication. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)."
|
||||
|
||||
@@ -7,6 +7,9 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- identity
|
||||
- access management
|
||||
---
|
||||
|
||||
Before adding a new GPG key to your {% data variables.product.product_name %} account, you should have:
|
||||
|
||||
@@ -7,6 +7,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- ssh
|
||||
---
|
||||
|
||||
Before adding a new SSH key to your {% data variables.product.product_name %} account, you should have:
|
||||
|
||||
@@ -7,6 +7,9 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- identity
|
||||
- access management
|
||||
---
|
||||
{% note %}
|
||||
|
||||
|
||||
@@ -9,5 +9,7 @@ redirect_from:
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- sso
|
||||
---
|
||||
|
||||
|
||||
@@ -6,6 +6,8 @@ redirect_from:
|
||||
- /articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- sso
|
||||
---
|
||||
|
||||
You can authorize an existing personal access token, or [create a new personal access token](/github/authenticating-to-github/creating-a-personal-access-token) and then authorize it.
|
||||
|
||||
@@ -6,6 +6,8 @@ redirect_from:
|
||||
- /articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- sso
|
||||
---
|
||||
|
||||
You can authorize an existing SSH key, or create a new SSH key and then authorize it. For more information about creating a new SSH key, see "[Generating a new SSH key and adding it to the ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)."
|
||||
|
||||
@@ -7,6 +7,9 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- identity
|
||||
- access management
|
||||
---
|
||||
|
||||
When an {% data variables.product.prodname_oauth_app %} wants to identify you by your {% data variables.product.product_name %} account, you'll see a page with the app's developer contact information and a list of the specific data that's being requested.
|
||||
|
||||
@@ -6,6 +6,8 @@ redirect_from:
|
||||
- /articles/changing-two-factor-authentication-delivery-methods-for-your-mobile-device
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- 2fa
|
||||
---
|
||||
|
||||
{% note %}
|
||||
|
||||
@@ -7,6 +7,9 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- identity
|
||||
- access management
|
||||
---
|
||||
{% data reusables.gpg.supported-gpg-key-algorithms %}
|
||||
|
||||
|
||||
@@ -7,6 +7,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- ssh
|
||||
---
|
||||
|
||||
{% data reusables.ssh.dsa-support %}
|
||||
|
||||
@@ -8,6 +8,9 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- identity
|
||||
- access management
|
||||
---
|
||||
|
||||
### Checking your commit signature verification status
|
||||
|
||||
@@ -11,6 +11,8 @@ redirect_from:
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
topics:
|
||||
- 2fa
|
||||
---
|
||||
|
||||
In addition to securely storing your two-factor authentication recovery codes, we strongly recommend configuring one or more additional recovery methods.
|
||||
|
||||
@@ -9,6 +9,8 @@ redirect_from:
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
topics:
|
||||
- 2fa
|
||||
---
|
||||
|
||||
You can configure two-factor authentication using a mobile app{% if currentVersion == "free-pro-team@latest" %} or via text message{% endif %}. You can also add a security key.
|
||||
|
||||
@@ -15,5 +15,7 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- ssh
|
||||
---
|
||||
|
||||
|
||||
@@ -7,6 +7,9 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- identity
|
||||
- access management
|
||||
---
|
||||
|
||||
When a third-party application wants to identify you by your {% data variables.product.product_name %} login, you'll see a page with the developer contact information and a list of the specific data that's being requested.
|
||||
|
||||
@@ -5,6 +5,8 @@ redirect_from:
|
||||
- /articles/countries-where-sms-authentication-is-supported
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- 2fa
|
||||
---
|
||||
|
||||
If we don't support two-factor authentication via text message for your country of residence, you can set up authentication via a TOTP mobile application. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)."
|
||||
|
||||
@@ -10,6 +10,9 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- identity
|
||||
- access management
|
||||
---
|
||||
|
||||
Personal access tokens (PATs) are an alternative to using passwords for authentication to {% data variables.product.product_name %} when using the [GitHub API](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens) or the [command line](#using-a-token-on-the-command-line).
|
||||
|
||||
@@ -7,6 +7,9 @@ redirect_from:
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
topics:
|
||||
- identity
|
||||
- access management
|
||||
---
|
||||
|
||||
You must choose or generate a password for your {% data variables.product.product_name %} account that is at least:
|
||||
|
||||
@@ -5,6 +5,8 @@ redirect_from:
|
||||
- /articles/deleted-or-missing-ssh-keys
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- ssh
|
||||
---
|
||||
|
||||
{% data variables.product.prodname_dotcom %} automatically deletes inactive SSH keys to help keep accounts safe, such as after someone leaves a job or loses a computer.
|
||||
|
||||
@@ -6,6 +6,8 @@ redirect_from:
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
topics:
|
||||
- 2fa
|
||||
---
|
||||
|
||||
We strongly recommend using two-factor authentication to secure your account. If you need to disable 2FA, we recommend re-enabling it as soon as possible.
|
||||
|
||||
@@ -8,6 +8,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- ssh
|
||||
---
|
||||
|
||||
When trying to SSH into {% data variables.product.product_location %} on a Linux computer, you may see the following message in your terminal:
|
||||
|
||||
@@ -7,6 +7,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- ssh
|
||||
---
|
||||
|
||||
When running remote Git commands or SSH, your connection might time out:
|
||||
|
||||
@@ -7,6 +7,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- ssh
|
||||
---
|
||||
|
||||
### Finding where the key has been used
|
||||
|
||||
@@ -7,6 +7,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- ssh
|
||||
---
|
||||
|
||||
### Should the `sudo` command be used with Git?
|
||||
|
||||
@@ -8,6 +8,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- ssh
|
||||
---
|
||||
|
||||
To fix this, the owner of the repository (`user`) needs to add your account (`other-user`) as a collaborator on the repository or to a team that has write access to the repository.
|
||||
|
||||
@@ -8,6 +8,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- ssh
|
||||
---
|
||||
|
||||
To fix this, remove the deploy key from the repository, and [add the key to your user account](/articles/adding-a-new-ssh-key-to-your-github-account) instead.
|
||||
|
||||
@@ -8,6 +8,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- ssh
|
||||
---
|
||||
|
||||
The `-K` option is in Apple's standard version of `ssh-add`, which stores the passphrase in your keychain for you when you add an ssh key to the ssh-agent. If you have installed a different version of `ssh-add`, it may lack support for `-K`.
|
||||
|
||||
@@ -5,6 +5,8 @@ redirect_from:
|
||||
- /articles/error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- ssh
|
||||
---
|
||||
The error you receive may look like the following:
|
||||
|
||||
|
||||
@@ -8,6 +8,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- ssh
|
||||
---
|
||||
|
||||
When using an unverified key to perform Git operations, you will be prompted to perform an audit of your SSH keys.
|
||||
|
||||
@@ -7,6 +7,9 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- identity
|
||||
- access management
|
||||
---
|
||||
|
||||
{% data reusables.gpg.supported-gpg-key-algorithms %}
|
||||
|
||||
@@ -9,6 +9,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- ssh
|
||||
---
|
||||
|
||||
If you don't already have an SSH key, you must [generate a new SSH key](#generating-a-new-ssh-key). If you're unsure whether you already have an SSH key, check for [existing keys](/articles/checking-for-existing-ssh-keys).
|
||||
|
||||
@@ -7,6 +7,9 @@ redirect_from:
|
||||
- /articles/githubs-ssh-key-fingerprints
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- identity
|
||||
- access management
|
||||
---
|
||||
|
||||
These are {% data variables.product.prodname_dotcom %}'s public key fingerprints:
|
||||
|
||||
@@ -17,6 +17,12 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- 2fa
|
||||
- identity
|
||||
- access management
|
||||
- usernames
|
||||
- device verification
|
||||
---
|
||||
|
||||
|
||||
|
||||
@@ -8,5 +8,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- identity
|
||||
- access management
|
||||
---
|
||||
|
||||
|
||||
@@ -10,5 +10,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- identity
|
||||
- access management
|
||||
---
|
||||
|
||||
|
||||
@@ -6,6 +6,9 @@ redirect_from:
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
topics:
|
||||
- identity
|
||||
- access management
|
||||
---
|
||||
|
||||
{% data variables.product.product_name %} requires a password to perform sensitive actions, such as adding new SSH keys, authorizing applications, or modifying team members.
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user