зеркало из https://github.com/github/docs.git
Remove GHAE in Liquid and front matter (22) (#49015)
This commit is contained in:
Peter Bengtsson
GitHub
Родитель
1262c33632
Коммит
d883f8d421
|
|
@ -15,8 +15,6 @@ This guide will walk you through setting up your {% data variables.product.compa
|
|||
The first steps in starting with {% data variables.product.product_name %} are to create an account, choose a product that fits your needs best, verify your email, set up two-factor authentication, and view your profile.
|
||||
{% elsif ghes %}
|
||||
The first steps in starting with {% data variables.product.product_name %} are to access your account, set up two-factor authentication, and view your profile.
|
||||
{% elsif ghae %}
|
||||
The first steps in starting with {% data variables.product.product_name %} are to access your account and view your profile.
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %}There are several types of accounts on {% data variables.product.prodname_dotcom %}. {% endif %} Every person who uses {% data variables.product.product_name %} has their own personal account, which can be part of multiple organizations and teams. Your personal account is your identity on {% data variables.location.product_location %} and represents you as an individual.
|
||||
|
|
@ -50,10 +48,6 @@ To ensure you can use all the features in your {% data variables.product.product
|
|||
The administrator of your {% data variables.product.product_name %} instance will notify you about how to authenticate and access your account. The process varies depending on the authentication mode they have configured for the instance.
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghae %}
|
||||
You will receive an email notification once your enterprise owner for {% data variables.product.product_name %} has set up your account, allowing you to authenticate with SAML single sign-on (SSO) and access your account.
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghes or ghec %}
|
||||
|
||||
### {% ifversion fpt or ghec %}4.{% else %}2.{% endif %} Configuring two-factor authentication
|
||||
|
|
|
|||
|
|
@ -7,7 +7,6 @@ versions:
|
|||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
topics:
|
||||
- API
|
||||
---
|
||||
|
|
@ -27,9 +26,3 @@ Alternatively, you can download the latest version of the public schema here:
|
|||
[{% octicon "desktop-download" aria-label="Download" %} `schema.docs-enterprise.graphql`](/public/ghes-{{ allVersions[currentVersion].currentRelease }}/schema.docs-enterprise.graphql) ({{ allVersions[currentVersion].versionTitle }})
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghae %}
|
||||
|
||||
[{% octicon "desktop-download" aria-label="Download" %} `schema.docs-ghae.graphql`](/public/ghae/schema.docs-ghae.graphql) ({{ allVersions[currentVersion].versionTitle }})
|
||||
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -6,7 +6,6 @@ versions:
|
|||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghec: '*'
|
||||
ghae: '*'
|
||||
---
|
||||
|
||||
## About migration paths to GitHub
|
||||
|
|
@ -43,7 +42,7 @@ You can review the scope and tooling for your migration to {% data variables.pro
|
|||
- **Scope**: Source, history, and metadata
|
||||
- **Tooling**: {% data variables.product.prodname_importer_proper_name %}
|
||||
- **More information**:
|
||||
- "[AUTOTITLE]({% ifversion ghae %}/free-pro-team@latest{% endif %}/migrations/using-github-enterprise-importer)"
|
||||
- "[AUTOTITLE](/migrations/using-github-enterprise-importer)"
|
||||
- [{% data variables.product.prodname_expert_services %}](https://github.com/services/) website
|
||||
- **Caveats**:
|
||||
- {% data reusables.migrations.large-repositories-require-expert-services %}
|
||||
|
|
@ -54,7 +53,7 @@ You can review the scope and tooling for your migration to {% data variables.pro
|
|||
- **Scope**: Source, history, and metadata
|
||||
- **Tooling**: {% data variables.product.prodname_importer_proper_name %}
|
||||
- **More information**:
|
||||
- "[AUTOTITLE]({% ifversion ghae %}/free-pro-team@latest{% endif %}/migrations/using-github-enterprise-importer)"
|
||||
- "[AUTOTITLE](/migrations/using-github-enterprise-importer)"
|
||||
- [{% data variables.product.prodname_expert_services %}](https://github.com/services/) website
|
||||
- **Caveats**:
|
||||
- {% data reusables.migrations.large-repositories-require-expert-services %}
|
||||
|
|
@ -67,7 +66,7 @@ Migrations from {% data variables.product.prodname_dotcom_the_website %} include
|
|||
- **Scope**: Source, history, and metadata
|
||||
- **Tooling**: {% data variables.product.prodname_importer_proper_name %} or {% data variables.product.prodname_expert_services %}
|
||||
- **More information**:
|
||||
- "[AUTOTITLE]({% ifversion ghae %}/free-pro-team@latest{% endif %}/migrations/using-github-enterprise-importer)"
|
||||
- "[AUTOTITLE](/migrations/using-github-enterprise-importer)"
|
||||
- [{% data variables.product.prodname_expert_services %}](https://github.com/services/) website
|
||||
- **Caveats**:
|
||||
- {% data reusables.migrations.large-repositories-require-expert-services %}
|
||||
|
|
@ -77,7 +76,7 @@ Migrations from {% data variables.product.prodname_dotcom_the_website %} include
|
|||
|
||||
- **Scope**: Source, history, and metadata
|
||||
- **Tooling**: {% data variables.product.prodname_importer_proper_name %}
|
||||
- **More information**: "[AUTOTITLE]({% ifversion ghae %}/free-pro-team@latest{% endif %}/migrations/using-github-enterprise-importer)"
|
||||
- **More information**: "[AUTOTITLE](/migrations/using-github-enterprise-importer)"
|
||||
|
||||
### Azure DevOps Server to {% data variables.product.prodname_dotcom_the_website %}
|
||||
|
||||
|
|
@ -85,7 +84,7 @@ Migrations from {% data variables.product.prodname_dotcom_the_website %} include
|
|||
- **Tooling**: Migration to Azure DevOps Services, then {% data variables.product.prodname_importer_proper_name %}
|
||||
- **More information**:
|
||||
- [Migrate data from Azure DevOps Server to Azure DevOps Services](https://learn.microsoft.com/en-us/azure/devops/migrate/migration-overview?view=azure-devops) in the Microsoft Docs
|
||||
- "[AUTOTITLE]({% ifversion ghae %}/free-pro-team@latest{% endif %}/migrations/using-github-enterprise-importer)"
|
||||
- "[AUTOTITLE](/migrations/using-github-enterprise-importer)"
|
||||
- **Caveats**: If you can't migrate to Azure DevOps Services first, you must perform a "source and history" migration instead. For more information, "[Migrations from any Git repository to {% data variables.product.prodname_dotcom_the_website %}](#migrations-from-any-git-repository)."
|
||||
|
||||
### Bitbucket Cloud (Bitbucket.org) to {% data variables.product.prodname_dotcom_the_website %}
|
||||
|
|
@ -101,7 +100,7 @@ Migrations from {% data variables.product.prodname_dotcom_the_website %} include
|
|||
- **Scope**: Source, history, and metadata
|
||||
- **Tooling**: {% data variables.product.prodname_importer_proper_name %}
|
||||
- **More information**:
|
||||
- "[AUTOTITLE]({% ifversion ghae %}/free-pro-team@latest{% endif %}/migrations/using-github-enterprise-importer)"
|
||||
- "[AUTOTITLE](/migrations/using-github-enterprise-importer)"
|
||||
- [{% data variables.product.prodname_expert_services %}](https://github.com/services/) website
|
||||
- **Caveats**:
|
||||
- For complex repositories larger than around 5 GB, you may need to use `bbs-exporter` and Enterprise Cloud Importer instead. Enterprise Cloud Importer is only available for expert-led migrations.
|
||||
|
|
|
|||
|
|
@ -6,7 +6,6 @@ versions:
|
|||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghec: '*'
|
||||
ghae: '*'
|
||||
---
|
||||
|
||||
## About migrations
|
||||
|
|
@ -60,9 +59,9 @@ If you’re migrating from {% data variables.product.prodname_ghe_cloud %} or {%
|
|||
|
||||
{% data reusables.enterprise-migration-tool.gh-repo-stats-not-supported %}
|
||||
|
||||
If you’re migrating from Azure DevOps, we recommend the `inventory-report` command in the {% data variables.product.prodname_ado2gh_cli %}. The `inventory-report` command will connect with the Azure DevOps API, then build a simple CSV with some of the fields suggested above. For more information about how to install the {% data variables.product.prodname_ado2gh_cli %}, see "[AUTOTITLE]({% ifversion ghae %}/enterprise-cloud@latest{% endif %}/migrations/using-github-enterprise-importer/migrating-from-azure-devops-to-github-enterprise-cloud/migrating-repositories-from-azure-devops-to-github-enterprise-cloud)."
|
||||
If you’re migrating from Azure DevOps, we recommend the `inventory-report` command in the {% data variables.product.prodname_ado2gh_cli %}. The `inventory-report` command will connect with the Azure DevOps API, then build a simple CSV with some of the fields suggested above. For more information about how to install the {% data variables.product.prodname_ado2gh_cli %}, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-from-azure-devops-to-github-enterprise-cloud/migrating-repositories-from-azure-devops-to-github-enterprise-cloud)."
|
||||
|
||||
If you’re migrating from Bitbucket Server or Bitbucket Data Center, we recommend the `inventory-report` command in the {% data variables.product.prodname_bbs2gh_cli %}. The `inventory-report` command will use your Bitbucket instance's API to build a simple CSV. For more information about how to install the {% data variables.product.prodname_bbs2gh_cli %}, see "[AUTOTITLE]({% ifversion ghae %}/enterprise-cloud@latest{% endif %}/migrations/using-github-enterprise-importer/migrating-from-bitbucket-server-to-github-enterprise-cloud/migrating-repositories-from-bitbucket-server-to-github-enterprise-cloud)."
|
||||
If you’re migrating from Bitbucket Server or Bitbucket Data Center, we recommend the `inventory-report` command in the {% data variables.product.prodname_bbs2gh_cli %}. The `inventory-report` command will use your Bitbucket instance's API to build a simple CSV. For more information about how to install the {% data variables.product.prodname_bbs2gh_cli %}, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-from-bitbucket-server-to-github-enterprise-cloud/migrating-repositories-from-bitbucket-server-to-github-enterprise-cloud)."
|
||||
|
||||
For other migration origins, create your migration inventory yourself. You could build the spreadsheet using the origin’s reporting tools, if available, or API, or you could create the inventory manually.
|
||||
|
||||
|
|
@ -202,7 +201,7 @@ For example, suppose @octocat created an issue on {% data variables.location.pro
|
|||
The way that attribution works differs between tools:
|
||||
|
||||
- If you’re using `ghe-migrator`, `gl-exporter`, or `bbs-exporter`, you will decide how you want to attribute data ahead of time and include a mapping file when you import your data.
|
||||
- If you’re using {% data variables.product.prodname_importer_proper_name %}, data will be linked to placeholder identities called “mannequins”, and you can assign this history to real users after your data is migrated. For more information, see "[AUTOTITLE]({% ifversion ghae %}/free-pro-team@latest{% endif %}/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/reclaiming-mannequins-for-github-enterprise-importer)."
|
||||
- If you’re using {% data variables.product.prodname_importer_proper_name %}, data will be linked to placeholder identities called “mannequins”, and you can assign this history to real users after your data is migrated. For more information, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/reclaiming-mannequins-for-github-enterprise-importer)."
|
||||
|
||||
### Managing teams and permissions
|
||||
|
||||
|
|
|
|||
|
|
@ -35,8 +35,6 @@ The page that's displayed allows you to enable or disable all security and analy
|
|||
|
||||
{% ifversion ghes %}If you have a license for {% data variables.product.prodname_GH_advanced_security %}, the page will also contain options to enable and disable {% data variables.product.prodname_advanced_security %} features. Any repositories that use {% data variables.product.prodname_GH_advanced_security %} are listed at the bottom of the page.{% endif %}
|
||||
|
||||
{% ifversion ghae %}The page will also contain options to enable and disable {% data variables.product.prodname_advanced_security %} features. Any repositories that use {% data variables.product.prodname_GH_advanced_security %} are listed at the bottom of the page.{% endif %}
|
||||
|
||||
## Enabling or disabling a feature for all existing repositories
|
||||
|
||||
You can enable or disable features for all repositories.
|
||||
|
|
@ -179,6 +177,6 @@ You can manage access to {% data variables.product.prodname_GH_advanced_security
|
|||
## Further reading
|
||||
|
||||
- "[AUTOTITLE](/code-security/getting-started/securing-your-repository)"{% ifversion not fpt %}
|
||||
- "[AUTOTITLE](/code-security/secret-scanning/about-secret-scanning)"{% endif %}{% ifversion not ghae %}
|
||||
- "[AUTOTITLE](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)"{% endif %}
|
||||
- "[AUTOTITLE](/code-security/secret-scanning/about-secret-scanning)"{% endif %}
|
||||
- "[AUTOTITLE](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)"
|
||||
- "[AUTOTITLE](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)"
|
||||
|
|
|
|||
|
|
@ -9,7 +9,6 @@ redirect_from:
|
|||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Organizations
|
||||
|
|
@ -202,7 +201,6 @@ Some of the features listed below are limited to organizations using {% data var
|
|||
| [Export a list of people with access to an organization repository](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/viewing-people-with-access-to-your-repository#exporting-a-list-of-people-with-access-to-your-repository) | {% octicon "check" aria-label="Yes" %} | {% octicon "x" aria-label="No" %} | {% octicon "x" aria-label="No" %} |
|
||||
| Manage default labels (see "[AUTOTITLE](/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization)") | {% octicon "check" aria-label="Yes" %} | {% octicon "x" aria-label="No" %} | {% octicon "x" aria-label="No" %} |{% ifversion pull-request-approval-limit %}
|
||||
| Manage pull request reviews in the organization (see "[AUTOTITLE](/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization)") | {% octicon "check" aria-label="Yes" %} | {% octicon "x" aria-label="No" %} | {% octicon "x" aria-label="No" %} | {% octicon "x" aria-label="No" %} |{% endif %}
|
||||
{% ifversion ghae %}| Manage IP allow lists (see "[AUTOTITLE](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list)") | {% octicon "check" aria-label="Yes" %} | {% octicon "x" aria-label="No" %} | {% octicon "x" aria-label="No" %} |{% endif %}
|
||||
|
||||
{% endrowheaders %}
|
||||
|
||||
|
|
@ -247,7 +245,6 @@ Some of the features listed below are limited to organizations using {% data var
|
|||
| [View people with access to an organization repository](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/viewing-people-with-access-to-your-repository) | {% octicon "check" aria-label="Yes" %} | {% octicon "x" aria-label="No" %} |
|
||||
| [Export a list of people with access to an organization repository](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/viewing-people-with-access-to-your-repository#exporting-a-list-of-people-with-access-to-your-repository) | {% octicon "check" aria-label="Yes" %} | {% octicon "x" aria-label="No" %} |
|
||||
| Manage default labels (see "[AUTOTITLE](/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization)") | {% octicon "check" aria-label="Yes" %} | {% octicon "x" aria-label="No" %} |
|
||||
{% ifversion ghae %}| Manage IP allow lists (see "[AUTOTITLE](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list)") | {% octicon "check" aria-label="Yes" %} | {% octicon "x" aria-label="No" %} |{% endif %}
|
||||
|
||||
{% endrowheaders %}
|
||||
|
||||
|
|
|
|||
|
|
@ -5,7 +5,6 @@ redirect_from:
|
|||
- /github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group
|
||||
permissions: 'Organization owners and team maintainers can synchronize a {% data variables.product.prodname_dotcom %} team with an IdP group.'
|
||||
versions:
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
feature: scim-for-ghes
|
||||
topics:
|
||||
|
|
@ -20,7 +19,7 @@ shortTitle: Synchronize with an IdP
|
|||
|
||||
{% data reusables.identity-and-permissions.about-team-sync %} {% ifversion ghec %}For more information, see "[AUTOTITLE](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)" and "[AUTOTITLE](/admin/identity-and-access-management/managing-iam-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)."{% endif %}
|
||||
|
||||
{% ifversion ghec %}You can connect up to five IdP groups to a {% data variables.product.product_name %} team.{% elsif ghae %}You can connect a team on {% data variables.product.product_name %} to one IdP group. All users in the group are automatically added to the team and also added to the parent organization as members. When you disconnect a group from a team, users who became members of the organization via team membership are removed from the organization.{% endif %} You can assign an IdP group to multiple {% data variables.product.product_name %} teams.
|
||||
{% ifversion ghec %}You can connect up to five IdP groups to a {% data variables.product.product_name %} team.{% endif %} You can assign an IdP group to multiple {% data variables.product.product_name %} teams.
|
||||
|
||||
{% ifversion ghec %}Team synchronization does not support IdP groups with more than 5000 members.{% endif %}
|
||||
|
||||
|
|
@ -37,10 +36,6 @@ All team membership changes made through your IdP will appear in the audit log o
|
|||
Connecting a team to an IdP group may remove some team members. For more information, see "[Requirements for members of synchronized teams](#requirements-for-members-of-synchronized-teams)."
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghae %}
|
||||
When group membership changes on your IdP, your IdP sends a SCIM request with the changes to {% data variables.product.product_name %} according to the schedule determined by your IdP. Any requests that change {% data variables.product.prodname_dotcom %} team or organization membership will register in the audit log as changes made by the account used to configure user provisioning. For more information about this account, see "[AUTOTITLE](/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-with-scim-for-your-enterprise)." For more information about SCIM request schedules, see "[Check the status of user provisioning](https://docs.microsoft.com/en-us/azure/active-directory/app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user)" in the Microsoft Docs.
|
||||
{% endif %}
|
||||
|
||||
Parent teams cannot synchronize with IdP groups. If the team you want to connect to an IdP group is a parent team, we recommend creating a new team or removing the nested relationships that make your team a parent team. For more information, see "[AUTOTITLE](/organizations/organizing-members-into-teams/about-teams#nested-teams)," "[AUTOTITLE](/organizations/organizing-members-into-teams/creating-a-team)," and "[AUTOTITLE](/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy)."
|
||||
|
||||
To manage repository access for any {% data variables.product.prodname_dotcom %} team, including teams connected to an IdP group, you must make changes with {% data variables.product.product_name %}. For more information, see "[AUTOTITLE](/organizations/organizing-members-into-teams/about-teams)" and "[AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/managing-team-access-to-an-organization-repository)."
|
||||
|
|
@ -78,11 +73,6 @@ To avoid unintentionally removing team members, visit the administrative portal
|
|||
|
||||
You must authenticate using SAML SSO. For more information, see "[AUTOTITLE](/authentication/authenticating-with-saml-single-sign-on)."
|
||||
|
||||
{% elsif ghae %}
|
||||
Before you can connect a {% data variables.product.product_name %} team with an IdP group, you must first configure user provisioning for {% data variables.location.product_location %} using a supported System for Cross-domain Identity Management (SCIM). For more information, see "[AUTOTITLE](/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-with-scim-for-your-enterprise)."
|
||||
|
||||
Once user provisioning for {% data variables.product.product_name %} is configured using SCIM, you can assign the {% data variables.product.product_name %} application to every IdP group that you want to use on {% data variables.product.product_name %}. For more information, see [Configure automatic user provisioning to GitHub AE](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-ae-provisioning-tutorial#step-5-configure-automatic-user-provisioning-to-github-ae) in the Microsoft Docs.
|
||||
|
||||
{% elsif scim-for-ghes %}
|
||||
You must configure user provisioning with SCIM for {% data variables.location.product_location %}. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-with-scim-for-your-enterprise)."
|
||||
|
||||
|
|
@ -91,7 +81,7 @@ You must configure user provisioning with SCIM for {% data variables.location.pr
|
|||
|
||||
## Connecting an IdP group to a team
|
||||
|
||||
When you connect an IdP group to a {% data variables.product.product_name %} team, all users in the group are automatically added to the team. {% ifversion ghae %}Any users who were not already members of the parent organization members are also added to the organization.{% endif %}
|
||||
When you connect an IdP group to a {% data variables.product.product_name %} team, all users in the group are automatically added to the team.
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.user-settings.access_org %}
|
||||
|
|
@ -99,8 +89,6 @@ When you connect an IdP group to a {% data variables.product.product_name %} tea
|
|||
{% data reusables.organizations.team_settings %}
|
||||
{%- ifversion ghec %}
|
||||
1. Under "Identity Provider Groups", select the **Select Groups** dropdown menu, and click up to 5 identity provider groups.
|
||||
{%- elsif ghae %}
|
||||
1. Under "Identity Provider Group", select the **Select Group** dropdown menu, and click an identity provider group from the list.
|
||||
{%- endif %}
|
||||
1. Click **Save changes**.
|
||||
|
||||
|
|
@ -112,9 +100,5 @@ When you connect an IdP group to a {% data variables.product.product_name %} tea
|
|||
{% data reusables.organizations.team_settings %}
|
||||
{%- ifversion ghec %}
|
||||
1. Under "Identity Provider Groups", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="Remove group" %}.
|
||||
{%- elsif ghae %}
|
||||
1. Under "Identity Provider Group", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="Remove group" %}.
|
||||
|
||||
|
||||
{%- endif %}
|
||||
1. Click **Save changes**.
|
||||
|
|
|
|||
|
|
@ -170,7 +170,7 @@ jobs:
|
|||
- name: Log in to GitHub Docker Registry
|
||||
uses: docker/login-action@65b78e6e13532edd9afa3aa52ac7964289d1a9c1
|
||||
with:
|
||||
registry: {% ifversion ghae %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}
|
||||
registry: docker.pkg.github.com
|
||||
username: {% raw %}${{ github.actor }}{% endraw %}
|
||||
password: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
|
||||
# This step uses the `docker/build-push-action` action to build the image, based on your repository's `Dockerfile`. If the build succeeds, it pushes the image to {% data variables.product.prodname_registry %}.
|
||||
|
|
@ -180,7 +180,7 @@ jobs:
|
|||
with:
|
||||
push: true
|
||||
tags: |
|
||||
{% ifversion ghae %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}/{% raw %}${{ github.repository }}/octo-image:${{ github.sha }}{% endraw %}
|
||||
docker.pkg.github.com/{% raw %}${{ github.repository }}/octo-image:${{ github.sha }}{% endraw %}
|
||||
```
|
||||
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -190,11 +190,7 @@ You can install packages from {% data variables.product.prodname_registry %} by
|
|||
|
||||
By default, you can add packages from one organization. For more information, see "[Installing packages from other organizations](#installing-packages-from-other-organizations)."
|
||||
|
||||
You also need to add the _.npmrc_ file to your project so that all requests to install packages will {% ifversion ghae %}be routed to{% else %}go through{% endif %} {% data variables.product.prodname_registry %}. {% ifversion fpt or ghes or ghec %}When you route all package requests through {% data variables.product.prodname_registry %}, you can use both scoped and unscoped packages from _npmjs.org_. For more information, see "[npm-scope](https://docs.npmjs.com/misc/scope)" in the npm documentation.{% endif %}
|
||||
|
||||
{% ifversion ghae %}
|
||||
By default, you can only use npm packages hosted on your enterprise, and you will not be able to use unscoped packages. For more information on package scoping, see "[npm-scope](https://docs.npmjs.com/misc/scope)" in the npm documentation. If required, {% data variables.product.prodname_dotcom %} support can enable an upstream proxy to npmjs.org. Once an upstream proxy is enabled, if a requested package isn't found on your enterprise, {% data variables.product.prodname_registry %} makes a proxy request to npmjs.org.
|
||||
{% endif %}
|
||||
You also need to add the _.npmrc_ file to your project so that all requests to install packages will go through {% data variables.product.prodname_registry %}. {% ifversion fpt or ghes or ghec %}When you route all package requests through {% data variables.product.prodname_registry %}, you can use both scoped and unscoped packages from _npmjs.org_. For more information, see "[npm-scope](https://docs.npmjs.com/misc/scope)" in the npm documentation.{% endif %}
|
||||
|
||||
{% data reusables.package_registry.authenticate-step %}
|
||||
{% data reusables.package_registry.create-npmrc-owner-step %}
|
||||
|
|
|
|||
|
|
@ -5,11 +5,10 @@ redirect_from:
|
|||
- /articles/why-are-my-commits-linked-to-the-wrong-user
|
||||
- /github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user
|
||||
- /github/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user
|
||||
intro: '{% data variables.product.product_name %} uses the email address in the commit header to link the commit to a GitHub user. If your commits are being linked to another user, or not linked to a user at all, you may need to change your local Git configuration settings{% ifversion not ghae %}, add an email address to your account email settings, or do both{% endif %}.'
|
||||
intro: '{% data variables.product.product_name %} uses the email address in the commit header to link the commit to a GitHub user. If your commits are being linked to another user, or not linked to a user at all, you may need to change your local Git configuration settings, add an email address to your account email settings, or do both.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
shortTitle: Linked to wrong user
|
||||
---
|
||||
|
|
@ -21,10 +20,10 @@ shortTitle: Linked to wrong user
|
|||
|
||||
## Commits are linked to another user
|
||||
|
||||
If your commits are linked to another user, that means the email address in your local Git configuration settings is connected to that user's account on {% data variables.product.product_name %}. In this case, you can change the email in your local Git configuration settings{% ifversion ghae %} to the address associated with your account on {% data variables.product.product_name %} to link your future commits. Old commits will not be linked. For more information, see "[AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address#setting-your-commit-email-address-in-git)."{% else %} and add the new email address to your account on {% data variables.location.product_location %} account to link future commits to your account.
|
||||
If your commits are linked to another user, that means the email address in your local Git configuration settings is connected to that user's account on {% data variables.product.product_name %}. In this case, you can change the email in your local Git configuration settings and add the new email address to your account on {% data variables.location.product_location %} account to link future commits to your account.
|
||||
|
||||
1. To change the email address in your local Git configuration, follow the steps in "[AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address#setting-your-commit-email-address-in-git)". If you work on multiple machines, you will need to change this setting on each one.
|
||||
1. Add the email address from step 2 to your account settings by following the steps in "[AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account)".{% endif %}
|
||||
1. Add the email address from step 2 to your account settings by following the steps in "[AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account)".
|
||||
|
||||
Commits you make from this point forward will be linked to your account.
|
||||
|
||||
|
|
@ -37,13 +36,9 @@ If your commits are not linked to any user, the commit author's name will not be
|
|||
{% data reusables.repositories.navigate-to-commit %}
|
||||
1. To read a message about why the commit is not linked, hover over the blue {% octicon "question" aria-label="Question mark" %} to the right of the username.
|
||||
|
||||
- **Unrecognized author (with email address)** If you see this message with an email address, the address you used to author the commit is not connected to your account on {% data variables.product.product_name %}. {% ifversion not ghae %}To link your commits, [add the email address to your GitHub email settings](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account).{% endif %}{% ifversion not ghae %} If the email address has a Gravatar associated with it, the Gravatar will be displayed next to the commit, rather than the default gray Octocat.{% endif %}
|
||||
- **Unrecognized author (no email address)** If you see this message without an email address, you used a generic email address that can't be connected to your account on {% data variables.product.product_name %}.{% ifversion not ghae %} You will need to [set your commit email address in Git](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address), then [add the new address to your GitHub email settings](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account) to link your future commits. Old commits will not be linked.{% endif %}
|
||||
- **Invalid email** The email address in your local Git configuration settings is either blank or not formatted as an email address.{% ifversion not ghae %} You will need to [set your commit email address in Git](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address), then [add the new address to your GitHub email settings](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account) to link your future commits. Old commits will not be linked.{% endif %}
|
||||
|
||||
{% ifversion ghae %}
|
||||
You can change the email in your local Git configuration settings to the address associated with your account to link your future commits. Old commits will not be linked. For more information, see "[AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address#setting-your-commit-email-address-in-git)."
|
||||
{% endif %}
|
||||
- **Unrecognized author (with email address)** If you see this message with an email address, the address you used to author the commit is not connected to your account on {% data variables.product.product_name %}. To link your commits, [add the email address to your GitHub email settings](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account). If the email address has a Gravatar associated with it, the Gravatar will be displayed next to the commit, rather than the default gray Octocat.
|
||||
- **Unrecognized author (no email address)** If you see this message without an email address, you used a generic email address that can't be connected to your account on {% data variables.product.product_name %}. You will need to [set your commit email address in Git](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address), then [add the new address to your GitHub email settings](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account) to link your future commits. Old commits will not be linked.
|
||||
- **Invalid email** The email address in your local Git configuration settings is either blank or not formatted as an email address. You will need to [set your commit email address in Git](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address), then [add the new address to your GitHub email settings](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account) to link your future commits. Old commits will not be linked.
|
||||
|
||||
{% warning %}
|
||||
|
||||
|
|
|
|||
|
|
@ -17,7 +17,6 @@ redirect_from:
|
|||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Repositories
|
||||
|
|
@ -30,8 +29,7 @@ Prerequisites for repository transfers:
|
|||
- When you transfer a repository that you own to another personal account, the new owner will receive a confirmation email.{% ifversion fpt or ghec %} The confirmation email includes instructions for accepting the transfer. If the new owner doesn't accept the transfer within one day, the invitation will expire.{% endif %}
|
||||
- To transfer a repository that you own to an organization, you must have permission to create a repository in the target organization.
|
||||
- The target account must not have a repository with the same name, or a fork in the same network.
|
||||
- The original owner of the repository is added as a collaborator on the transferred repository. Other collaborators to the transferred repository remain intact.{% ifversion ghae %}
|
||||
- Internal repositories can't be transferred.{% endif %}
|
||||
- The original owner of the repository is added as a collaborator on the transferred repository. Other collaborators to the transferred repository remain intact.
|
||||
- Single repositories forked from a private upstream network cannot be transferred.
|
||||
{%- ifversion ghec %}
|
||||
- Internal repositories can only be transferred to an organization in the enterprise. You cannot transfer an internal repository from an organization owned by one enterprise account to an organization owned by a different enterprise account.
|
||||
|
|
|
|||
|
|
@ -12,7 +12,6 @@ redirect_from:
|
|||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
|
|
@ -65,8 +64,7 @@ You can manage the security and analysis features for your {% ifversion fpt or g
|
|||
|
||||
**Note:** If you disable {% data variables.product.prodname_GH_advanced_security %}, {% ifversion ghec %}dependency review, {% endif %}{% data variables.secret-scanning.user_alerts %} and {% data variables.product.prodname_code_scanning %} are disabled. Any workflows, SARIF uploads, or API calls for {% data variables.product.prodname_code_scanning %} will fail. If {% data variables.product.prodname_GH_advanced_security %} is re-enabled, {% data variables.product.prodname_code_scanning %} will return to its previous state.
|
||||
{% endnote %}{% endif %}
|
||||
{% endif %}{% ifversion ghae %}
|
||||
1. Under "Code security and analysis", to the right of the feature, click **Disable** or **Enable**. Before you can enable "{% data variables.product.prodname_secret_scanning %}" for your repository, you may need to enable {% data variables.product.prodname_GH_advanced_security %}.{% endif %}
|
||||
{% endif %}
|
||||
|
||||
## Granting access to security alerts
|
||||
|
||||
|
|
|
|||
|
|
@ -9,7 +9,6 @@ redirect_from:
|
|||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
shortTitle: Git Large File Storage
|
||||
---
|
||||
|
|
@ -27,7 +26,7 @@ Different maximum size limits for {% data variables.large_files.product_name_sho
|
|||
| {% data variables.product.prodname_pro %} | 2 GB |
|
||||
| {% data variables.product.prodname_team %} | 4 GB |
|
||||
| {% data variables.product.prodname_ghe_cloud %} | 5 GB |{% else %}
|
||||
Using {% data variables.large_files.product_name_short %}, you can store files up to {% ifversion ghae %}200 MiB{% else %}5 GB{% endif %} in your repository.
|
||||
Using {% data variables.large_files.product_name_short %}, you can store files up to 5 GB in your repository.
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.repositories.git-lfs %}
|
||||
|
|
|
|||
|
|
@ -49,7 +49,7 @@ Git is not designed to handle large SQL files. To share large databases with oth
|
|||
|
||||
### Repository size limits
|
||||
|
||||
We recommend repositories remain small, ideally less than 1 GB, and less than 5 GB is strongly recommended. {% ifversion ghae %}The maximum size for a repository on {% data variables.product.product_name %} is 100 GB. {% endif %}Smaller repositories are faster to clone and easier to work with and maintain. If your repository excessively impacts our infrastructure, you might receive an email from {% data variables.contact.github_support %} asking you to take corrective action. We try to be flexible, especially with large projects that have many collaborators, and will work with you to find a resolution whenever possible. You can prevent your repository from impacting our infrastructure by effectively managing your repository's size and overall health. You can find advice and a tool for repository analysis in the [`github/git-sizer`](https://github.com/github/git-sizer) repository.
|
||||
We recommend repositories remain small, ideally less than 1 GB, and less than 5 GB is strongly recommended. Smaller repositories are faster to clone and easier to work with and maintain. If your repository excessively impacts our infrastructure, you might receive an email from {% data variables.contact.github_support %} asking you to take corrective action. We try to be flexible, especially with large projects that have many collaborators, and will work with you to find a resolution whenever possible. You can prevent your repository from impacting our infrastructure by effectively managing your repository's size and overall health. You can find advice and a tool for repository analysis in the [`github/git-sizer`](https://github.com/github/git-sizer) repository.
|
||||
|
||||
External dependencies can cause Git repositories to become very large. To avoid filling a repository with external dependencies, we recommend you use a package manager. Popular package managers for common languages include [Bundler](http://bundler.io/), [Node's Package Manager](http://npmjs.org/), and [Maven](https://maven.apache.org/). These package managers support using Git repositories directly, so you don't need pre-packaged sources.
|
||||
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
title: Users
|
||||
intro: >-
|
||||
Use the REST API to suspend{% ifversion ghes %}, unsuspend, promote, and
|
||||
demote{% endif %}{% ifversion ghae %} and unsuspend{% endif %} users on your
|
||||
demote{% endif %} users on your
|
||||
enterprise.
|
||||
versions: # DO NOT MANUALLY EDIT. CHANGES WILL BE OVERWRITTEN BY A 🤖
|
||||
ghae: '*'
|
||||
|
|
|
|||
|
|
@ -5,7 +5,6 @@ intro: 'Learn about REST API rate limits, how to avoid exceeding them, and what
|
|||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- API
|
||||
|
|
@ -41,7 +40,7 @@ The primary rate limit for unauthenticated requests is 60 requests per hour.
|
|||
|
||||
You can use a {% data variables.product.pat_generic %} to make API requests. Additionally, you can authorize a {% data variables.product.prodname_github_app %} or {% data variables.product.prodname_oauth_app %}, which can then make API requests on your behalf.
|
||||
|
||||
All of these requests count towards your personal rate limit of {% ifversion ghae %}15,000{% else %}5,000{% endif %} requests per hour. {% ifversion fpt or ghec %}Requests made on your behalf by a {% data variables.product.prodname_github_app %} that is owned by a {% data variables.product.prodname_ghe_cloud %} organization have a higher rate limit of 15,000 requests per hour. Similarly, requests made on your behalf by a {% data variables.product.prodname_oauth_app %} that is owned or approved by a {% data variables.product.prodname_ghe_cloud %} organization have a higher rate limit of 15,000 requests per hour if you are a member of the {% data variables.product.prodname_ghe_cloud %} organization.{% endif %}
|
||||
All of these requests count towards your personal rate limit of 5,000 requests per hour. {% ifversion fpt or ghec %}Requests made on your behalf by a {% data variables.product.prodname_github_app %} that is owned by a {% data variables.product.prodname_ghe_cloud %} organization have a higher rate limit of 15,000 requests per hour. Similarly, requests made on your behalf by a {% data variables.product.prodname_oauth_app %} that is owned or approved by a {% data variables.product.prodname_ghe_cloud %} organization have a higher rate limit of 15,000 requests per hour if you are a member of the {% data variables.product.prodname_ghe_cloud %} organization.{% endif %}
|
||||
|
||||
### Primary rate limit for {% data variables.product.prodname_github_app %} installations
|
||||
|
||||
|
|
|
|||
|
|
@ -11,14 +11,13 @@ redirect_from:
|
|||
- /github/searching-for-information-on-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-in-github-enterprise-server
|
||||
versions:
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
topics:
|
||||
- GitHub search
|
||||
---
|
||||
|
||||
## About search for {% data variables.product.prodname_dotcom_the_website %} repositories from {% data variables.product.product_name %}
|
||||
|
||||
You can search for designated private repositories on {% data variables.product.prodname_ghe_cloud %} from {% data variables.location.product_location %}{% ifversion ghae %} on {% data variables.product.prodname_ghe_managed %}{% endif %}. For more information about searching across environments, see "[AUTOTITLE](/search-github/getting-started-with-searching-on-github/about-searching-on-github#searching-repositories-on-githubcom-from-your-private-enterprise-environment)."
|
||||
You can search for designated private repositories on {% data variables.product.prodname_ghe_cloud %} from {% data variables.location.product_location %}. For more information about searching across environments, see "[AUTOTITLE](/search-github/getting-started-with-searching-on-github/about-searching-on-github#searching-repositories-on-githubcom-from-your-private-enterprise-environment)."
|
||||
|
||||
## Prerequisites
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Contacting GitHub Support
|
||||
shortTitle: Contacting support
|
||||
intro: 'You can use the {% ifversion ghae %}{% data variables.contact.ae_azure_portal %}{% else %}{% data variables.contact.landing_page_portal %}{% endif %} to contact GitHub Support for help troubleshooting issues you encounter while using GitHub.'
|
||||
intro: 'You can use the {% data variables.contact.landing_page_portal %} to contact GitHub Support for help troubleshooting issues you encounter while using GitHub.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
|
|
|
|||
|
|
@ -257,7 +257,7 @@
|
|||
description: >-
|
||||
A gist is a shareable file that you can edit, clone, and fork on GitHub.
|
||||
You can make a gist public or secret, although secret gists will be
|
||||
available to {% ifversion ghae %}any enterprise member{% else %}anyone{% endif %} with the URL.
|
||||
available to anyone with the URL.
|
||||
- term: Git
|
||||
description: >-
|
||||
Git is an open source program for tracking changes in text files. It was
|
||||
|
|
|
|||
|
|
@ -1,6 +1,3 @@
|
|||
{% ifversion ghae %}
|
||||
To allow your self-hosted runners to communicate with {% data variables.product.prodname_dotcom %}, add the IP address or IP address range of your self-hosted runners to the IP allow list. For more information, see "[Adding an allowed IP address](#adding-an-allowed-ip-address)."
|
||||
{% else %}
|
||||
{% warning %}
|
||||
|
||||
**Warning**: If you use an IP allow list and would also like to use {% data variables.product.prodname_actions %}, you must use self-hosted runners{% ifversion actions-hosted-runners %} or {% data variables.product.prodname_dotcom %}-hosted larger runners with static IP address ranges{% endif %}. For more information, see "[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners)" {% ifversion actions-hosted-runners %} or "[AUTOTITLE](/actions/using-github-hosted-runners/using-larger-runners)"{% endif %}.
|
||||
|
|
@ -8,4 +5,3 @@ To allow your self-hosted runners to communicate with {% data variables.product.
|
|||
{% endwarning %}
|
||||
|
||||
To allow your self-hosted {% ifversion actions-hosted-runners %}or larger hosted{% endif %} runners to communicate with {% data variables.product.prodname_dotcom %}, add the IP address or IP address range of your runners to the IP allow list that you have configured for your enterprise.
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
{% ifversion ghes %}By default, user access token{% else %}User access token{% endif %} requests are limited to {% ifversion ghae %}15,000{% elsif fpt or ghec or ghes %}5,000{% endif %} requests per hour and per authenticated user. All requests from {% data variables.product.prodname_oauth_apps %} authorized by a user or a {% data variables.product.pat_generic %} owned by the user, and requests authenticated with any of the user's authentication credentials, share the same quota of {% ifversion ghae %}15,000{% elsif fpt or ghec or ghes %}5,000{% endif %} requests per hour for that user.
|
||||
{% ifversion ghes %}By default, user access token{% else %}User access token{% endif %} requests are limited to 5,000 requests per hour and per authenticated user. All requests from {% data variables.product.prodname_oauth_apps %} authorized by a user or a {% data variables.product.pat_generic %} owned by the user, and requests authenticated with any of the user's authentication credentials, share the same quota of 5,000 requests per hour for that user.
|
||||
|
|
|
|||
Загрузка…
Ссылка в новой задаче