1
0
mirror of synced 2026-01-27 06:09:02 -05:00

Merge pull request #32510 from github/repo-sync

Repo sync
This commit is contained in:
docs-bot
2024-04-15 10:28:49 -04:00
committed by GitHub
10 changed files with 23 additions and 11 deletions

View File

@@ -83,6 +83,9 @@ To configure provisioning, the setup user with the **@<em>SHORT-CODE</em>_admin*
1. To make changes, click **Edit**.
1. Select **Enable API integration**.
1. In the "API Token" field, enter the {% data variables.product.pat_v1 %} with the **admin:enterprise** scope belonging to the setup user.
{% data reusables.scim.import-groups-unsupported %}
1. Click **Test API Credentials**. If the test is successful, a verification message will appear at the top of the screen.
1. To save the token, click **Save**.
1. In the settings menu, click **To App**.

View File

@@ -62,6 +62,8 @@ You can also configure and manage team synchronization for an individual organiz
## Managing whether team synchronization can re-invite non-members to organizations
{% data reusables.saml.team-sync-pending-invites %}
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.settings-tab %}
{% data reusables.enterprise-accounts.security-tab %}

View File

@@ -8,7 +8,7 @@ redirect_from:
- /admin/user-management/managing-repositories-in-your-enterprise//migrating-to-internal-repositories
permissions: Site administrators can migrate to internal repositories.
versions:
ghes: '*'
ghes: '<3.10'
type: how_to
topics:
- Enterprise

View File

@@ -17,7 +17,7 @@ One of the main differences between {% data variables.product.product_name %} an
{% data reusables.enterprise.ghe-includes-ghec-and-ghes %} For more information about {% data variables.product.prodname_ghe_server %} and how it differs from {% data variables.product.prodname_ghe_cloud %}, see "[AUTOTITLE](/admin/overview/about-github-for-enterprises#about-deployment-options)."
## About identity and access management
## About enterprise types
Before you start using {% data variables.product.product_name %}, you must decide whether you want to allow your developers to create and manage their own personal accounts, or whether you want to use {% data variables.product.prodname_emus %}, which allows you to create and manage the user accounts for your developers through your IdP.
@@ -25,7 +25,7 @@ If you choose {% data variables.product.prodname_emus %}, all user accounts must
If you choose not to use {% data variables.product.prodname_emus %}, your developers will create their own personal accounts on {% data variables.product.prodname_dotcom_the_website %}, but you can optionally require SAML authentication before those personal accounts can access your enterprise's resources.
To help you decide which choice is best for your enterprise, see "[AUTOTITLE](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)."
To help you decide which choice is best for your enterprise, see "[AUTOTITLE](/admin/identity-and-access-management/understanding-iam-for-enterprises/choosing-an-enterprise-type-for-github-enterprise-cloud)."
## About documentation

View File

@@ -55,7 +55,7 @@ Recommendations, best practices or product hints. Tips contain non-essential inf
For example, "[AUTOTITLE](/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile)" uses a tip callout to help users understand what to expect when they @mention an organization.
>[!TIP] When you @mention an organization, only those that you're a member of will autocomplete. You can still @mention organizations that you're not a member of, like a previous employer, but the organization name won't autocomplete for you.
> [!TIP] When you @mention an organization, only those that you're a member of will autocomplete. You can still @mention organizations that you're not a member of, like a previous employer, but the organization name won't autocomplete for you.
#### Note
@@ -67,7 +67,7 @@ Notes are particularly useful for communicating parenthetical information that i
For example, "[AUTOTITLE](/code-security/secret-scanning/managing-alerts-from-secret-scanning#reviewing-github-token-metadata)" uses a note to inform users that metadata for {% data variables.product.prodname_dotcom %} tokens is currently in beta.
>[!NOTE] Metadata for {% data variables.product.prodname_dotcom %} tokens is currently in public beta and subject to change.
> [!NOTE] Metadata for {% data variables.product.prodname_dotcom %} tokens is currently in public beta and subject to change.
#### Warning
@@ -77,7 +77,7 @@ Warning callouts are particularly relevant for processes that occur outside the
For example, "[AUTOTITLE](/enterprise-cloud@latest/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)" includes instructions for the command line, and uses a warning callout to alert users that once issued, certificates cannot be revoked:
>[!WARNING] After a certificate has been signed and issued, the certificate cannot be revoked. Make sure to use the -V flag to configure a lifetime for the certificate, or the certificate can be used indefinitely.
> [!WARNING] After a certificate has been signed and issued, the certificate cannot be revoked. Make sure to use the -V flag to configure a lifetime for the certificate, or the certificate can be used indefinitely.
#### Danger
@@ -94,25 +94,25 @@ Callouts are rendered using Markdown.
Tip:
```markdown
>[!TIP] Here's a suggestion.
> [!TIP] Here's a suggestion.
```
Note:
```markdown
>[!NOTE] Keep this in mind.
> [!NOTE] Keep this in mind.
```
Warning:
```markdown
>[!WARNING] Be careful.
> [!WARNING] Be careful.
```
Danger:
```markdown
>[!DANGER] Be extremely careful.
> [!DANGER] Be extremely careful.
```
Liquid syntax for callouts is still supported and may still appear in older articles, but should not be used for new callouts.

View File

@@ -98,6 +98,8 @@ For help on provisioning users that have missing a missing SCIM linked identity,
## Managing whether team sync can re-invite non-members to your organization
{% data reusables.saml.team-sync-pending-invites %}
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
{% data reusables.organizations.security %}

View File

@@ -1 +1,3 @@
1. Select **Enable API integration**.
{% data reusables.scim.import-groups-unsupported %}

View File

@@ -0,0 +1 @@
Changes to this setting do **not** impact pending invitations. Any invitation generated while team sync was allowed to re-invite past members to the organization can result in the member being re-added to the organization, even if re-invitation has since been disallowed.

View File

@@ -0,0 +1 @@
>[!NOTE] "Import Groups" is **not** supported by {% data variables.product.prodname_dotcom %}. Selecting or deselecting the checkbox has no impact on your configuration.

View File

@@ -1,6 +1,7 @@
If your support request is outside of the scope of what our team can help you with, we may recommend next steps to resolve your issue outside of {% data variables.contact.github_support %}. Your support request is possibly out of {% data variables.contact.github_support %}'s scope if the request is primarily about:
- Third party integrations, such as Jira{% ifversion ghes %}
- Third party integrations, such as Jira
- Enterprise Cloud Importer (available only with expert-led migrations){% ifversion ghes %}
- Hardware setup{% endif %}
- CI/CD, such as Jenkins
- Writing scripts