Remove product_name from various reusables folders (#54135)
This commit is contained in:
Isaac Brown
@@ -1,3 +1,3 @@
|
||||
{% ifversion fpt or ghec %}
|
||||
To keep your email address private, use your {% data variables.product.product_name %}-provided `no-reply` email address.
|
||||
To keep your email address private, use your {% data variables.product.github %}-provided `no-reply` email address.
|
||||
{% endif %}
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
|
||||
### Supported GPG key algorithms
|
||||
|
||||
{% data variables.product.product_name %} supports several GPG key algorithms. If you try to add a key generated with an unsupported algorithm, you may encounter an error.
|
||||
{% data variables.product.github %} supports several GPG key algorithms. If you try to add a key generated with an unsupported algorithm, you may encounter an error.
|
||||
|
||||
* RSA
|
||||
* ElGamal
|
||||
|
||||
@@ -1 +1 @@
|
||||
If team sync is enabled for your organization or enterprise account, you can synchronize a {% data variables.product.prodname_dotcom %} team with an IdP group. When you synchronize a {% data variables.product.prodname_dotcom %} team with an IdP group, membership changes to the IdP group are reflected on {% data variables.product.product_name %} automatically, reducing the need for manual updates and custom scripts.
|
||||
If team sync is enabled for your organization or enterprise account, you can synchronize a {% data variables.product.github %} team with an IdP group. When you do this, membership changes to the IdP group are reflected on {% data variables.product.github %} automatically, reducing the need for manual updates and custom scripts.
|
||||
|
||||
@@ -1 +1 @@
|
||||
To connect a team on {% data variables.product.product_name %} to an IdP group, the team must already exist in your organization. Even if you have configured SCIM provisioning, creating a group in your IdP does not automatically create a team on {% data variables.product.product_name %}.
|
||||
To connect a team on {% data variables.product.github %} to an IdP group, the team must already exist in your organization. Even if you have configured SCIM provisioning, creating a group in your IdP does not automatically create a team on {% data variables.product.github %}.
|
||||
|
||||
@@ -1 +1 @@
|
||||
You can check the verification status of your signed commits or tags on {% data variables.product.product_name %} and view why your commit signatures might be unverified. For more information, see [AUTOTITLE](/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status).
|
||||
You can check the verification status of your signed commits or tags on {% data variables.product.github %} and view why your commit signatures might be unverified. For more information, see [AUTOTITLE](/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status).
|
||||
|
||||
@@ -1 +1 @@
|
||||
When restrictions are enabled, only the specified type of {% data variables.product.product_name %} user will be able to participate in interactions. Restrictions automatically expire after a defined duration.
|
||||
When restrictions are enabled, only the specified type of {% data variables.product.github %} user will be able to participate in interactions. Restrictions automatically expire after a defined duration.
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
{% ifversion fpt or ghec %}
|
||||
You can choose whether {% data variables.large_files.product_name_short %} objects are included in [source code archives](/repositories/working-with-files/using-files/downloading-source-code-archives), such as ZIP files and tarballs, that {% data variables.product.product_name %} creates for your repository. For more information, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository).
|
||||
You can choose whether {% data variables.large_files.product_name_short %} objects are included in [source code archives](/repositories/working-with-files/using-files/downloading-source-code-archives), such as ZIP files and tarballs, that {% data variables.product.github %} creates for your repository. For more information, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository).
|
||||
{% endif %}
|
||||
|
||||
@@ -1 +1 @@
|
||||
Users cannot push {% data variables.large_files.product_name_short %} assets to {% data variables.product.product_name %} if {% data variables.large_files.product_name_short %} is disabled on the enterprise or repository.
|
||||
Users cannot push {% data variables.large_files.product_name_short %} assets to {% data variables.product.github %} if {% data variables.large_files.product_name_short %} is disabled on the enterprise or repository.
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
1. To open {% data variables.product.prodname_marketplace %}, in the top-left corner of {% data variables.product.prodname_dotcom %}, select {% octicon "three-bars" aria-label="Open global navigation menu" %}, then click **{% octicon "gift" aria-hidden="true" %} Marketplace**.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1 +1 @@
|
||||
1. Create a new repository on {% data variables.product.github %}. To avoid errors, do not initialize the new repository with README, license, or gitignore files. You can add these files after your project has been pushed to {% data variables.product.product_name %}. For more information, see [AUTOTITLE](/repositories/creating-and-managing-repositories/creating-a-new-repository).
|
||||
1. Create a new repository on {% data variables.product.github %}. To avoid errors, do not initialize the new repository with README, license, or gitignore files. You can add these files after your project has been pushed to {% data variables.product.github %}. For more information, see [AUTOTITLE](/repositories/creating-and-managing-repositories/creating-a-new-repository).
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
1. To push the repository to {% data variables.product.prodname_dotcom %}, run `git push --mirror origin`.
|
||||
|
||||
If your repository contains any files that are larger than {% data variables.product.product_name %}'s file size limit, your push may fail. Move the large files to {% data variables.large_files.product_name_short %} by running `git lfs import`, then try again.
|
||||
If your repository contains any files that are larger than {% data variables.product.github %}'s file size limit, your push may fail. Move the large files to {% data variables.large_files.product_name_short %} by running `git lfs import`, then try again.
|
||||
|
||||
@@ -1 +1 @@
|
||||
When you follow organizations on {% data variables.product.product_name %}, you'll see their {% ifversion fpt or ghec %}public{% endif %} activity on your personal dashboard. This activity includes new discussions, sponsorships, and repositories.
|
||||
When you follow organizations on {% data variables.product.github %}, you'll see their {% ifversion fpt or ghec %}public{% endif %} activity on your personal dashboard. This activity includes new discussions, sponsorships, and repositories.
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
Your team can collaborate on {% data variables.product.product_name %} by using an organization account, which serves as a container for your shared work and gives the work a unique name and brand.
|
||||
Your team can collaborate on {% data variables.product.github %} by using an organization account, which serves as a container for your shared work and gives the work a unique name and brand.
|
||||
|
||||
Each person that uses {% data variables.product.prodname_dotcom %} always signs into a personal account, and multiple personal accounts can collaborate on shared projects by joining the same organization account. A subset of these personal accounts can be given the role of organization owner, which allows those people to granularly manage access to the organization's resources using sophisticated security and administrative features.
|
||||
|
||||
@@ -1 +1 @@
|
||||
When you issue each client certificate, you must include an extension that specifies which {% data variables.product.product_name %} user the certificate is for. For more information, see [AUTOTITLE](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities).
|
||||
When you issue each client certificate, you must include an extension that specifies which {% data variables.product.github %} user the certificate is for. For more information, see [AUTOTITLE](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities).
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
|
||||
You need an access token to publish, install, and delete private, internal, and public packages.
|
||||
|
||||
You can use a {% data variables.product.pat_v1 %} to authenticate to {% data variables.product.prodname_registry %} or the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API. When you create a {% data variables.product.pat_v1 %}, you can assign the token different scopes depending on your needs. For more information about packages-related scopes for a {% data variables.product.pat_v1 %}, see [AUTOTITLE](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries).
|
||||
You can use a {% data variables.product.pat_v1 %} to authenticate to {% data variables.product.prodname_registry %} or the {% data variables.product.github %} API. When you create a {% data variables.product.pat_v1 %}, you can assign the token different scopes depending on your needs. For more information about packages-related scopes for a {% data variables.product.pat_v1 %}, see [AUTOTITLE](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries).
|
||||
|
||||
To authenticate to a {% data variables.product.prodname_registry %} registry within a {% data variables.product.prodname_actions %} workflow, you can use:
|
||||
* `GITHUB_TOKEN` to publish packages associated with the workflow repository.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
{% ifversion ghes %}
|
||||
|
||||
>[!NOTE] {% data variables.product.prodname_container_registry %} is currently in {% data variables.release-phases.public_preview %} for {% data variables.product.product_name %} and subject to change.
|
||||
>[!NOTE] {% data variables.product.prodname_container_registry %} is currently in {% data variables.release-phases.public_preview %} for {% data variables.product.prodname_ghe_server %} and subject to change.
|
||||
|
||||
Both {% data variables.product.prodname_registry %} and subdomain isolation must be enabled to use {% data variables.product.prodname_container_registry %}. For more information, see [AUTOTITLE](/packages/working-with-a-github-packages-registry/working-with-the-container-registry).
|
||||
|
||||
|
||||
@@ -1 +1 @@
|
||||
{% data variables.product.product_name %} 3.6 supports migration for Docker images stored in organizations. A future release will support migration of user-owned images.
|
||||
{% data variables.product.prodname_ghe_server %} 3.6 supports migration for Docker images stored in organizations. A future release will support migration of user-owned images.
|
||||
|
||||
@@ -1,2 +1,2 @@
|
||||
> [!NOTE]
|
||||
> The {% data variables.product.prodname_registry %} Docker registry {% ifversion ghes %} will be superseded in a future {% data variables.product.product_name %} release with the {% data variables.product.prodname_container_registry %}, which offers improved container support.{% elsif fpt %} is superseded by the {% data variables.product.prodname_container_registry %}, which offers improved container support. {% endif %} {% ifversion fpt or ghec %} For more information, see [AUTOTITLE](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry). {% endif %}
|
||||
> The {% data variables.product.prodname_registry %} Docker registry {% ifversion ghes %} will be superseded in a future {% data variables.product.prodname_ghe_server %} release with the {% data variables.product.prodname_container_registry %}, which offers improved container support.{% elsif fpt %} is superseded by the {% data variables.product.prodname_container_registry %}, which offers improved container support. {% endif %} {% ifversion fpt or ghec %} For more information, see [AUTOTITLE](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry). {% endif %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
{% ifversion ghes %}
|
||||
|
||||
> [!NOTE]
|
||||
> {% data variables.product.prodname_registry %} on {% data variables.product.product_name %} does not currently support clustering.
|
||||
> {% data variables.product.prodname_registry %} on {% data variables.product.prodname_ghe_server %} does not currently support clustering.
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -1 +1 @@
|
||||
1. If you use a static site generator to build your site locally and push the generated files to {% data variables.product.product_name %}, pull the commit that added the CNAME file to your local repository. For more information, see [AUTOTITLE](/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages#cname-errors).
|
||||
1. If you use a static site generator to build your site locally and push the generated files to {% data variables.product.github %}, pull the commit that added the CNAME file to your local repository. For more information, see [AUTOTITLE](/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages#cname-errors).
|
||||
|
||||
@@ -1 +1 @@
|
||||
Before you can create your site, you must have a repository for your site on {% data variables.product.product_name %}. If you're not creating your site in an existing repository, see [Creating a repository for your site](#creating-a-repository-for-your-site).
|
||||
Before you can create your site, you must have a repository for your site on {% data variables.product.github %}. If you're not creating your site in an existing repository, see [Creating a repository for your site](#creating-a-repository-for-your-site).
|
||||
|
||||
@@ -1 +1 @@
|
||||
1. On {% data variables.product.product_name %}, navigate to your site's repository.
|
||||
1. On {% data variables.product.github %}, navigate to your site's repository.
|
||||
|
||||
@@ -2,4 +2,4 @@ You can publish your site when changes are pushed to a specific branch, or you c
|
||||
|
||||
If you do not need any control over the build process for your site, we recommend that you publish your site when changes are pushed to a specific branch. {% data reusables.pages.pages-about-branch-source %}
|
||||
|
||||
If you want to use a build process other than Jekyll or you do not want a dedicated branch to hold your compiled static files, we recommend that you write a {% data variables.product.prodname_actions %} workflow to publish your site. {% data variables.product.product_name %} provides workflow templates for common publishing scenarios to help you write your workflow.
|
||||
If you want to use a build process other than Jekyll or you do not want a dedicated branch to hold your compiled static files, we recommend that you write a {% data variables.product.prodname_actions %} workflow to publish your site. {% data variables.product.github %} provides workflow templates for common publishing scenarios to help you write your workflow.
|
||||
|
||||
@@ -1 +1 @@
|
||||
If you are publishing from a branch, changes to your site are published automatically when the changes are merged into your site's publishing source. If you are publishing from a custom {% data variables.product.prodname_actions %} workflow, changes are published whenever your workflow is triggered (typically by a push to the default branch). If you want to preview your changes first, you can make the changes locally instead of on {% data variables.product.product_name %}. Then, test your site locally. For more information, see [AUTOTITLE](/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll).
|
||||
If you are publishing from a branch, changes to your site are published automatically when the changes are merged into your site's publishing source. If you are publishing from a custom {% data variables.product.prodname_actions %} workflow, changes are published whenever your workflow is triggered (typically by a push to the default branch). If you want to preview your changes first, you can make the changes locally instead of on {% data variables.product.github %}. Then, test your site locally. For more information, see [AUTOTITLE](/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll).
|
||||
|
||||
@@ -1,2 +1,2 @@
|
||||
> [!NOTE]
|
||||
> It can take up to 10 minutes for changes to your site to publish after you push the changes to {% data variables.product.product_name %}. If you don't see your {% data variables.product.prodname_pages %} site changes reflected in your browser after an hour, see [AUTOTITLE](/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites).
|
||||
> It can take up to 10 minutes for changes to your site to publish after you push the changes to {% data variables.product.github %}. If you don't see your {% data variables.product.prodname_pages %} site changes reflected in your browser after an hour, see [AUTOTITLE](/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites).
|
||||
|
||||
@@ -1 +1 @@
|
||||
1. In the upper-right corner of any {% data variables.product.product_name %} page, click your profile photo, then click **Your profile**.
|
||||
1. In the upper-right corner of any page, click your profile photo, then click **Your profile**.
|
||||
|
||||
@@ -1 +1 @@
|
||||
Your pronouns will only be visible to users that are signed in to {% data variables.product.product_name %}.
|
||||
Your pronouns will only be visible to users that are signed in to {% data variables.product.github %}.
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
{% data variables.product.product_name %} marks an issue or pull request as updated when it is:
|
||||
{% data variables.product.github %} marks an issue or pull request as updated when it is:
|
||||
|
||||
* Created
|
||||
* Reopened
|
||||
|
||||
@@ -1 +1 @@
|
||||
1. Collect the name and email address for each co-author.{% ifversion fpt or ghec %} If a person chooses to keep their email address private, you should use their {% data variables.product.product_name %}-provided `no-reply` email to protect their privacy.{% endif %}
|
||||
1. Collect the name and email address for each co-author.{% ifversion fpt or ghec %} If a person chooses to keep their email address private, you should use their {% data variables.product.github %}-provided `no-reply` email to protect their privacy.{% endif %}
|
||||
|
||||
@@ -1 +1 @@
|
||||
{% data variables.product.product_name %} merges the pull request according to the merge strategy configured in the branch protection once all required CI checks pass.
|
||||
{% data variables.product.github %} merges the pull request according to the merge strategy configured in the branch protection once all required CI checks pass.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
When you select the **Rebase and merge** option on a pull request, all commits from the topic branch (or head branch) are added onto the base branch individually without a merge commit. In that way, the rebase and merge behavior resembles a [fast-forward merge](https://git-scm.com/docs/git-merge#_fast_forward_merge) by maintaining a linear project history. However, rebasing achieves this by re-writing the commit history on the base branch with new commits.
|
||||
|
||||
The rebase and merge behavior on {% data variables.product.product_name %} deviates slightly from `git rebase`. Rebase and merge on {% data variables.product.prodname_dotcom %} will always update the committer information and create new commit SHAs, whereas `git rebase` outside of {% data variables.product.prodname_dotcom %} does not change the committer information when the rebase happens on top of an ancestor commit. For more information about `git rebase`, see [git-rebase](https://git-scm.com/docs/git-rebase) in the Git documentation.
|
||||
The rebase and merge behavior on {% data variables.product.github %} deviates slightly from `git rebase`. Rebase and merge on {% data variables.product.prodname_dotcom %} will always update the committer information and create new commit SHAs, whereas `git rebase` outside of {% data variables.product.prodname_dotcom %} does not change the committer information when the rebase happens on top of an ancestor commit. For more information about `git rebase`, see [git-rebase](https://git-scm.com/docs/git-rebase) in the Git documentation.
|
||||
|
||||
To rebase and merge pull requests, you must have [write permissions](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization) in the repository, and the repository must [allow rebase merging](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests).
|
||||
|
||||
|
||||
@@ -1 +1 @@
|
||||
{% data variables.product.product_name %} will only trigger reminders for up to five repositories per owner and 20 pull requests per repository. Reminders are not sent when changes are merged from upstream into a fork.
|
||||
{% data variables.product.github %} will only trigger reminders for up to five repositories per owner and 20 pull requests per repository. Reminders are not sent when changes are merged from upstream into a fork.
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
{% ifversion fpt or ghec %}
|
||||
When you type a password to sign in, create an account, or change your password, {% data variables.product.product_name %} will check if the password you entered is considered weak according to datasets like HaveIBeenPwned. The password may be identified as weak even if you have never used that password before.
|
||||
When you type a password to sign in, create an account, or change your password, {% data variables.product.github %} will check if the password you entered is considered weak according to datasets like HaveIBeenPwned. The password may be identified as weak even if you have never used that password before.
|
||||
|
||||
{% data variables.product.product_name %} only inspects the password at the time you type it, and never stores the password you entered in plaintext. For more information, see [HaveIBeenPwned](https://haveibeenpwned.com/).
|
||||
{% data variables.product.github %} only inspects the password at the time you type it, and never stores the password you entered in plaintext. For more information, see [HaveIBeenPwned](https://haveibeenpwned.com/).
|
||||
{% endif %}
|
||||
|
||||
@@ -1 +1 @@
|
||||
You can launch projects from a repository on {% data variables.location.product_location %} to your server by using a deploy key, which is an SSH key that grants access to a single repository. {% data variables.product.product_name %} attaches the public part of the key directly to your repository instead of a personal account, and the private part of the key remains on your server. For more information, see [AUTOTITLE](/rest/guides/delivering-deployments).
|
||||
You can launch projects from a repository on {% data variables.location.product_location %} to your server by using a deploy key, which is an SSH key that grants access to a single repository. {% data variables.product.github %} attaches the public part of the key directly to your repository instead of a personal account, and the private part of the key remains on your server. For more information, see [AUTOTITLE](/rest/guides/delivering-deployments).
|
||||
|
||||
@@ -6,12 +6,12 @@ A relative link is a link that is relative to the current file. For example, if
|
||||
[Contribution guidelines for this project](docs/CONTRIBUTING.md)
|
||||
```
|
||||
|
||||
{% data variables.product.product_name %} will automatically transform your relative link or image path based on whatever branch you're currently on, so that the link or path always works. The path of the link will be relative to the current file. Links starting with `/` will be relative to the repository root. You can use all relative link operands, such as `./` and `../`.
|
||||
{% data variables.product.github %} will automatically transform your relative link or image path based on whatever branch you're currently on, so that the link or path always works. The path of the link will be relative to the current file. Links starting with `/` will be relative to the repository root. You can use all relative link operands, such as `./` and `../`.
|
||||
|
||||
Your link text should be on a single line. The example below will not work.
|
||||
|
||||
```markdown
|
||||
[Contribution
|
||||
[Contribution
|
||||
guidelines for this project](docs/CONTRIBUTING.md)
|
||||
```
|
||||
|
||||
|
||||
@@ -1 +1 @@
|
||||
1. Define the severity of the security vulnerability using the **Severity** dropdown menu. If you want to calculate a CVSS score, select **Assess severity using CVSS** and then select the appropriate values in the **Calculator**. The {% data variables.product.product_name %} calculates the score according to the [Common Vulnerability Scoring System Calculator](https://www.first.org/cvss/calculator).
|
||||
1. Define the severity of the security vulnerability using the **Severity** dropdown menu. If you want to calculate a CVSS score, select **Assess severity using CVSS** and then select the appropriate values in the **Calculator**. {% data variables.product.github %} calculates the score according to the [Common Vulnerability Scoring System Calculator](https://www.first.org/cvss/calculator).
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
The {% data variables.product.product_name %} REST API is versioned. The API version name is based on the date when the API version was released. For example, the API version `{{ initialRestVersioningReleaseDate }}` was released on {{ initialRestVersioningReleaseDateLong }}.
|
||||
The {% data variables.product.github %} REST API is versioned. The API version name is based on the date when the API version was released. For example, the API version `{{ initialRestVersioningReleaseDate }}` was released on {{ initialRestVersioningReleaseDateLong }}.
|
||||
|
||||
Any breaking changes will be released in a new API version. Breaking changes are changes that can potentially break an integration. Breaking changes include:
|
||||
|
||||
|
||||
@@ -1 +1 @@
|
||||
To access each organization's resources on {% data variables.product.product_name %}, the member must have an active SAML session in their browser.{% ifversion ghec %} To access each organization's protected resources using the API and Git, the member must use a {% data variables.product.pat_generic %} or SSH key that the member has authorized for use with the organization.{% endif %} Enterprise owners can view and revoke a member's {% ifversion ghec %}linked identity, active sessions, or authorized credentials{% else %}active SAML sessions{% endif %} at any time.
|
||||
To access each organization's resources on {% data variables.product.github %}, the member must have an active SAML session in their browser.{% ifversion ghec %} To access each organization's protected resources using the API and Git, the member must use a {% data variables.product.pat_generic %} or SSH key that the member has authorized for use with the organization.{% endif %} Enterprise owners can view and revoke a member's {% ifversion ghec %}linked identity, active sessions, or authorized credentials{% else %}active SAML sessions{% endif %} at any time.
|
||||
|
||||
@@ -1 +1 @@
|
||||
You must create and use a dedicated machine user account on your IdP to associate with an enterprise owner account on {% data variables.product.product_name %}. Store the credentials for the user account securely in a password manager. For more information, see [AUTOTITLE](/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-with-scim-for-your-enterprise#enabling-user-provisioning-for-your-enterprise).
|
||||
You must create and use a dedicated machine user account on your IdP to associate with an enterprise owner account on {% data variables.product.github %}. Store the credentials for the user account securely in a password manager. For more information, see [AUTOTITLE](/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-with-scim-for-your-enterprise#enabling-user-provisioning-for-your-enterprise).
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
## Error: "Current time is earlier than NotBefore condition"
|
||||
|
||||
This error can occur when there's too large of a time difference between your IdP and {% data variables.product.product_name %}, which commonly occurs with self-hosted IdPs.
|
||||
This error can occur when there's too large of a time difference between your IdP and {% data variables.product.github %}, which commonly occurs with self-hosted IdPs.
|
||||
|
||||
{% ifversion ghes %}To prevent this problem, we recommend pointing your appliance to the same Network Time Protocol (NTP) source as your IdP, if possible. {% endif %}If you encounter this error, make sure the time on your {% ifversion ghes %}appliance{% else %}IdP{% endif %} is properly synced with your NTP server. {% ifversion ghes %}You can use the `chronyc` command on the administrative shell to synchronize time immediately. For more information, see [AUTOTITLE](/admin/configuration/configuring-network-settings/configuring-time-synchronization#correcting-a-large-time-drift).{% endif %}
|
||||
|
||||
|
||||
@@ -1 +1 @@
|
||||
SAML single sign-on (SSO) gives organization owners and enterprise owners using {% data variables.product.product_name %} a way to control and secure access to organization resources like repositories, issues, and pull requests.
|
||||
SAML single sign-on (SSO) gives organization owners and enterprise owners a way to control and secure access to organization resources like repositories, issues, and pull requests.
|
||||
|
||||
@@ -1 +1 @@
|
||||
When you use {% ifversion ghec %}{% data variables.product.prodname_emus %}{% else %}an IdP for IAM on {% data variables.product.product_name %}{% endif %}, SAML SSO controls and secures access to enterprise resources like repositories, issues, and pull requests. SCIM automatically creates user accounts and manages access to your enterprise when you make changes on your IdP. You can also synchronize teams on {% data variables.product.github %} with groups on your IdP.
|
||||
When you use {% ifversion ghec %}{% data variables.product.prodname_emus %}{% else %}an IdP for IAM on {% data variables.product.prodname_ghe_server %}{% endif %}, SAML SSO controls and secures access to enterprise resources like repositories, issues, and pull requests. SCIM automatically creates user accounts and manages access to your enterprise when you make changes on your IdP. You can also synchronize teams on {% data variables.product.github %} with groups on your IdP.
|
||||
|
||||
@@ -1 +1 @@
|
||||
When SAML SSO is disabled, all linked external identities are removed from {% data variables.product.product_name %}.
|
||||
When SAML SSO is disabled, all linked external identities are removed from {% data variables.product.github %}.
|
||||
|
||||
@@ -1 +1 @@
|
||||
{% data variables.product.product_name %} does not support SAML Single Logout. To terminate an active SAML session, users should log out directly on your SAML IdP.
|
||||
{% data variables.product.github %} does not support SAML Single Logout. To terminate an active SAML session, users should log out directly on your SAML IdP.
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
{% data variables.product.product_name %} supports SAML SSO with IdPs that implement the SAML 2.0 standard. For more information, see the [SAML Wiki](https://wiki.oasis-open.org/security) on the OASIS website.
|
||||
{% data variables.product.github %} supports SAML SSO with IdPs that implement the SAML 2.0 standard. For more information, see the [SAML Wiki](https://wiki.oasis-open.org/security) on the OASIS website.
|
||||
|
||||
{% data variables.product.company_short %} officially supports and internally tests the following IdPs.
|
||||
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
By default, your IdP does not communicate with {% data variables.product.product_name %} automatically when you assign or unassign the application. {% data variables.product.product_name %} {% ifversion fpt or ghec %}provisions access to your resources on {% else %}creates a user account {% endif %}using SAML Just-in-Time (JIT) provisioning the first time someone navigates to {% ifversion fpt or ghec %}your resources on {% endif %} {% data variables.product.product_name %} and signs in by authenticating through your IdP. You may need to manually notify users when you grant access to {% data variables.product.product_name %}, and you must manually {% ifversion fpt or ghec %}deprovision access {% else %}deactivate the user account on {% endif %}{% data variables.product.product_name %} during offboarding.
|
||||
By default, your IdP does not communicate with {% data variables.product.github %} automatically when you assign or unassign the application. {% data variables.product.github %} {% ifversion fpt or ghec %}provisions access to your resources on {% else %}creates a user account {% endif %}using SAML Just-in-Time (JIT) provisioning the first time someone navigates to {% ifversion fpt or ghec %}your enterprise's resources on {% data variables.product.github %}{% else %}{% data variables.location.product_location_enterprise %}{% endif %} and signs in by authenticating through your IdP. You may need to manually notify users when you grant access to {% data variables.product.github %}, and you must manually {% ifversion fpt or ghec %}deprovision access {% else %}deactivate the user account on {% endif %}{% data variables.product.github %} during offboarding.
|
||||
|
||||
Alternatively, instead of SAML JIT provisioning, you can use SCIM to {% ifversion ghec %}provision or deprovision{% elsif ghes %}create or suspend{% endif %} {% ifversion fpt or ghec %}access to organizations owned by your enterprise on {% data variables.product.prodname_dotcom %} {% else %}user accounts and grant or deny access to {% data variables.location.product_location %} {% endif %}automatically after you assign or unassign the application on your IdP.{% ifversion ghes %} SCIM for {% data variables.product.product_name %} is currently in {% ifversion scim-for-ghes-public-beta %}public{% else %}private{% endif %} {% data variables.release-phases.public_preview %} and is subject to change.{% endif %}
|
||||
Alternatively, instead of SAML JIT provisioning, you can use SCIM to {% ifversion ghec %}provision or deprovision{% elsif ghes %}create or suspend{% endif %} {% ifversion fpt or ghec %}access to organizations owned by your enterprise on {% data variables.product.prodname_dotcom %} {% else %}user accounts and grant or deny access to {% data variables.location.product_location %} {% endif %}automatically after you assign or unassign the application on your IdP.{% ifversion ghes %} SCIM for {% data variables.product.prodname_ghe_server %} is currently in {% ifversion scim-for-ghes-public-beta %}public{% else %}private{% endif %} {% data variables.release-phases.public_preview %} and is subject to change.{% endif %}
|
||||
|
||||
@@ -1 +1 @@
|
||||
Before you configure provisioning, you must configure authentication for your users. This configuration requires setup on both your identity management system and {% data variables.product.product_name %}. For more information, see [AUTOTITLE](/admin/identity-and-access-management/configuring-authentication-for-enterprise-managed-users).
|
||||
Before you configure provisioning, you must configure authentication for your users. This configuration requires setup on both your identity management system and {% data variables.product.github %}. For more information, see [AUTOTITLE](/admin/identity-and-access-management/configuring-authentication-for-enterprise-managed-users).
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
{% ifversion ghec %}
|
||||
To avoid exceeding the rate limit on {% data variables.product.product_name %}, do not assign more than 1,000 users per hour to the SCIM integration on your IdP. If you use groups to assign users to the IdP application, do not add more than 1,000 users to each group per hour. If you exceed these thresholds, attempts to provision users may fail with a "rate limit" error. You can review your IdP logs to confirm if attempted SCIM provisioning or push operations failed due to a rate limit error. The response to a failed provisioning attempt will depend on the IdP.
|
||||
To avoid exceeding {% data variables.product.github %}'s rate limit, do not assign more than 1,000 users per hour to the SCIM integration on your IdP. If you use groups to assign users to the IdP application, do not add more than 1,000 users to each group per hour. If you exceed these thresholds, attempts to provision users may fail with a "rate limit" error. You can review your IdP logs to confirm if attempted SCIM provisioning or push operations failed due to a rate limit error. The response to a failed provisioning attempt will depend on the IdP.
|
||||
{% elsif ghes %}
|
||||
A site administrator may have enabled API rate limits on your instance. If you exceed these thresholds, attempts to provision users may fail with a "rate limit" error. You can review your IdP logs to confirm if attempted SCIM provisioning or push operations failed due to a rate limit error. The response to a failed provisioning attempt will depend on the IdP.
|
||||
{% endif %}
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
{% ifversion scim-for-ghes-public-beta %}
|
||||
|
||||
>[!NOTE] SCIM for {% data variables.product.product_name %} is currently in {% data variables.release-phases.public_preview %} and subject to change. {% data variables.product.company_short %} recommends testing with a staging instance first. See [AUTOTITLE](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance).
|
||||
>[!NOTE] SCIM for {% data variables.product.prodname_ghe_server %} is currently in {% data variables.release-phases.public_preview %} and subject to change. {% data variables.product.company_short %} recommends testing with a staging instance first. See [AUTOTITLE](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance).
|
||||
|
||||
{% elsif ghes < 3.14 %}
|
||||
|
||||
>[!NOTE] This is an outdated, {% data variables.release-phases.private_preview %} version of SCIM for {% data variables.product.product_name %}. Customers must upgrade to 3.14 or newer and use the {% data variables.product.product_name %} SCIM {% data variables.release-phases.public_preview %} in order for their SCIM feedback or bug reports to be considered.
|
||||
>[!NOTE] This is an outdated, {% data variables.release-phases.private_preview %} version of SCIM for {% data variables.product.prodname_ghe_server %}. Customers must upgrade to 3.14 or newer and use the SCIM {% data variables.release-phases.public_preview %} in order for their SCIM feedback or bug reports to be considered.
|
||||
|
||||
>[!WARNING] The {% data variables.release-phases.public_preview %} is exclusively for testing and feedback, and no support is available. {% data variables.product.company_short %} recommends testing with a staging instance. For more information, see [AUTOTITLE](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance).
|
||||
|
||||
|
||||
@@ -1 +1 @@
|
||||
1. On {% data variables.product.product_name %}, navigate to the profile of the user or organization you want to sponsor.
|
||||
1. On {% data variables.product.github %}, navigate to the profile of the user or organization you want to sponsor.
|
||||
|
||||
@@ -1 +1 @@
|
||||
1. On {% data variables.product.product_name %}, navigate to the sponsored account's profile.
|
||||
1. On {% data variables.product.github %}, navigate to the sponsored account's profile.
|
||||
|
||||
@@ -1 +1 @@
|
||||
You can connect with developers around the world to ask and answer questions, learn, and interact directly with {% data variables.product.product_name %} staff. To get the conversation started, see [{% data variables.product.prodname_gcf %}](https://github.com/orgs/community/discussions/).
|
||||
You can connect with developers around the world to ask and answer questions, learn, and interact directly with {% data variables.product.company_short %} staff. To get the conversation started, see [{% data variables.product.prodname_gcf %}](https://github.com/orgs/community/discussions/).
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
{% data variables.contact.enterprise_support %} may consider a ticket solved after providing an explanation, recommendation, usage instructions, workaround instructions{% ifversion ghes %}, or by advising you of an available release that addresses the issue{% endif %}.
|
||||
|
||||
{% ifversion ghes %}
|
||||
If you have installed additional third-party software on, or made modifications to, {% data variables.product.product_name %} outside of the recommendations of {% data variables.contact.enterprise_support %}, {% data variables.contact.enterprise_support %} may ask you to remove the software and/or modifications while attempting to resolve the issue. If the problem is fixed when the unsupported software or modifications have been removed, {% data variables.contact.enterprise_support %} may consider the ticket solved.
|
||||
If you have installed additional third-party software on, or made modifications to, {% data variables.product.prodname_ghe_server %} outside of the recommendations of {% data variables.contact.enterprise_support %}, {% data variables.contact.enterprise_support %} may ask you to remove the software and/or modifications while attempting to resolve the issue. If the problem is fixed when the unsupported software or modifications have been removed, {% data variables.contact.enterprise_support %} may consider the ticket solved.
|
||||
{% endif %}
|
||||
|
||||
{% data variables.contact.enterprise_support %} may close a ticket if the ticket is outside the scope of support or if multiple attempts to contact you have gone unanswered. If {% data variables.contact.enterprise_support %} closes a ticket due to lack of response, you can request that {% data variables.contact.enterprise_support %} reopen the ticket.
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
For questions, bug reports, and discussions about {% data variables.product.prodname_github_apps %}, {% data variables.product.prodname_oauth_apps %}, and API development, explore the {% data reusables.support.prodname_support_forum_with_url %}. The discussions are moderated and maintained by {% data variables.product.company_short %} staff, and answered by the {% data variables.product.company_short %} community.
|
||||
|
||||
Consider reaching out to [GitHub Support](https://support.github.com/) directly using the contact form for:
|
||||
* Guaranteed response from {% data variables.product.product_name %} staff
|
||||
* Guaranteed response from {% data variables.product.company_short %} staff
|
||||
* Support requests involving sensitive data or private concerns
|
||||
* Feature requests
|
||||
* Feedback about {% data variables.product.product_name %} products
|
||||
* Feedback about {% data variables.product.github %} products
|
||||
|
||||
@@ -1 +1 @@
|
||||
When you configure two-factor authentication, you'll download and save your 2FA recovery codes. If you lose access to your phone, you can authenticate to {% data variables.product.product_name %} using your recovery codes.
|
||||
When you configure two-factor authentication, you'll download and save your 2FA recovery codes. If you lose access to your phone, you can authenticate to {% data variables.product.github %} using your recovery codes.
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
1. Complete the CAPTCHA challenge, which helps protect against spam and abuse.
|
||||
1. Under "Verify account", select your country code and type your mobile phone number, including the area code. When your information is correct, click **Send authentication code**.
|
||||
1. You'll receive a text message with a security code. On {% data variables.product.product_name %}, type the code into the field under "Verify the code sent to your phone" and click **Continue**.
|
||||
1. You'll receive a text message with a security code. On {% data variables.product.github %}, type the code into the field under "Verify the code sent to your phone" and click **Continue**.
|
||||
|
||||
* If you need to edit the phone number you entered, you'll need to complete another CAPTCHA challenge.
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
1. Under "Scan the QR code", do one of the following:
|
||||
|
||||
* Scan the QR code with your mobile device's app. After scanning, the app displays a six-digit code that you can enter on {% data variables.product.product_name %}.
|
||||
* Scan the QR code with your mobile device's app. After scanning, the app displays a six-digit code that you can enter on {% data variables.product.github %}.
|
||||
* If you can't scan the QR code, click **setup key** to see a code, the TOTP secret, that you can manually enter in your TOTP app instead.
|
||||
|
||||
|
||||
|
||||
1. The TOTP application saves your account on {% data variables.location.product_location %} and generates a new authentication code every few seconds. On {% data variables.product.product_name %}, type the code into the field under "Verify the code from the app."
|
||||
1. The TOTP application saves your account on {% data variables.location.product_location %} and generates a new authentication code every few seconds. On {% data variables.product.github %}, type the code into the field under "Verify the code from the app."
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
Before using this method, be sure that you can receive text messages. Carrier rates may apply.
|
||||
|
||||
> [!WARNING]
|
||||
> We **strongly recommend** using a TOTP application for two-factor authentication instead of SMS, and security keys as backup methods instead of SMS. {% data variables.product.product_name %} doesn't support sending SMS messages to phones in every country. Before configuring authentication via text message, review the list of countries where {% data variables.product.product_name %} supports authentication via SMS. For more information, see [AUTOTITLE](/authentication/securing-your-account-with-two-factor-authentication-2fa/countries-where-sms-authentication-is-supported).
|
||||
> We **strongly recommend** using a TOTP application for two-factor authentication instead of SMS, and security keys as backup methods instead of SMS. {% data variables.product.github %} doesn't support sending SMS messages to phones in every country. Before configuring authentication via text message, review the list of countries where {% data variables.product.github %} supports authentication via SMS. For more information, see [AUTOTITLE](/authentication/securing-your-account-with-two-factor-authentication-2fa/countries-where-sms-authentication-is-supported).
|
||||
|
||||
@@ -1 +1 @@
|
||||
For security reasons, {% data variables.product.product_name %} Support [will not be able to restore access to accounts](/free-pro-team@latest/site-policy/other-site-policies/github-account-recovery-policy) with two-factor authentication enabled if you lose your two-factor authentication credentials or lose access to your account recovery methods.
|
||||
For security reasons, {% data variables.product.company_short %} Support [will not be able to restore access to accounts](/free-pro-team@latest/site-policy/other-site-policies/github-account-recovery-policy) with two-factor authentication enabled if you lose your two-factor authentication credentials or lose access to your account recovery methods.
|
||||
|
||||
@@ -1 +1 @@
|
||||
For more information on commit email addresses,{% ifversion fpt or ghec %} including your `noreply` email address for {% data variables.product.product_name %},{% endif %} see [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address).
|
||||
For more information on commit email addresses,{% ifversion fpt or ghec %} including your `noreply` email address for {% data variables.product.github %},{% endif %} see [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address).
|
||||
|
||||
@@ -1 +1 @@
|
||||
If you are frequently editing code snippets and tables, you may benefit from enabling a fixed-width font in all comment fields on {% data variables.product.product_name %}. For more information, see [AUTOTITLE](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github#enabling-fixed-width-fonts-in-the-editor).
|
||||
If you are frequently editing code snippets and tables, you may benefit from enabling a fixed-width font in all comment fields on {% data variables.product.github %}. For more information, see [AUTOTITLE](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github#enabling-fixed-width-fonts-in-the-editor).
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
{% ifversion fpt or ghec %}
|
||||
You can export and review the metadata that {% data variables.product.product_name %} stores about your personal account.
|
||||
You can export and review the metadata that {% data variables.product.github %} stores about your personal account.
|
||||
{% endif %}
|
||||
|
||||
@@ -1 +1 @@
|
||||
Add the email address to your account on {% data variables.product.product_name %}, so that your commits are attributed to you and appear in your contributions graph. For more information, see [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account).
|
||||
Add the email address to your account on {% data variables.product.github %}, so that your commits are attributed to you and appear in your contributions graph. For more information, see [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account).
|
||||
|
||||
@@ -1 +1 @@
|
||||
Set an email address in Git. You can use {% ifversion fpt or ghec %}your [{% data variables.product.product_name %}-provided `noreply` email address](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address#about-no-reply-email) or {% endif %}any email address.
|
||||
Set an email address in Git. You can use {% ifversion fpt or ghec %}your [{% data variables.product.github %}-provided `noreply` email address](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address#about-no-reply-email) or {% endif %}any email address.
|
||||
|
||||
@@ -1 +1 @@
|
||||
1. If prompted, confirm access to your account on {% data variables.product.product_name %}. For more information, see [AUTOTITLE](/authentication/keeping-your-account-and-data-secure/sudo-mode).
|
||||
1. If prompted, confirm access to your account on {% data variables.product.github %}. For more information, see [AUTOTITLE](/authentication/keeping-your-account-and-data-secure/sudo-mode).
|
||||
|
||||
@@ -1 +1 @@
|
||||
When a private repository is made public. Without a doubt: the best {% data variables.product.product_name %} event.
|
||||
When a private repository is made public.
|
||||
|
||||
@@ -1 +1 @@
|
||||
Setting a webhook secret allows you to ensure that `POST` requests sent to the payload URL are from {% data variables.product.product_name %}. When you set a secret, you'll receive the `X-Hub-Signature` and `X-Hub-Signature-256` headers in the webhook `POST` request. For more information on how to use a secret with a signature header to secure your webhook payloads, see [AUTOTITLE](/webhooks-and-events/webhooks/securing-your-webhooks).
|
||||
Setting a webhook secret allows you to ensure that `POST` requests sent to the payload URL are from {% data variables.product.github %}. When you set a secret, you'll receive the `X-Hub-Signature` and `X-Hub-Signature-256` headers in the webhook `POST` request. For more information on how to use a secret with a signature header to secure your webhook payloads, see [AUTOTITLE](/webhooks-and-events/webhooks/securing-your-webhooks).
|
||||
|
||||
Reference in New Issue
Block a user