зеркало из https://github.com/github/docs.git
Ran white space linter on content (#52996)
This commit is contained in:
Ashley
GitHub
Родитель
1367fa3214
Коммит
3b27662c5d
|
|
@ -24,7 +24,7 @@ allowTitleToDifferFromFilename: true
|
|||
|
||||
If you publicize your private contributions, people without access to the private repositories you work in won't be able to see the details of your private contributions. Instead, they'll see the number of private contributions you made on any given day. Your public contributions will include detailed information. For more information, see "[AUTOTITLE](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile)."
|
||||
|
||||
>[!NOTE] On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_name %}{% endif %}, public contributions on your profile are visible {% ifversion fpt or ghec %}to anyone in the world who can access {% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}only to other users of {% data variables.location.product_location%}{% endif %}.
|
||||
>[!NOTE] On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_name %}{% endif %}, public contributions on your profile are visible {% ifversion fpt or ghec %}to anyone in the world who can access {% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}only to other users of {% data variables.location.product_location %}{% endif %}.
|
||||
|
||||
## Changing the visibility of your private contributions
|
||||
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ Before you leave your company, make sure you update the following information in
|
|||
|
||||
If you've been working with repositories that belong to an organization, you'll want to [remove yourself as a member of the organization](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/removing-yourself-from-an-organization). Note that if you are the organization owner, you should first [transfer ownership of the organization](/organizations/managing-organization-settings/transferring-organization-ownership) to another person.
|
||||
|
||||
Unless you're using a {% data variables.enterprise.prodname_managed_user %}, you'll still be able to access your personal account, even after leaving the organization. For more information about {% data variables.product.prodname_emus %}, see "[About {% data variables.product.prodname_emus %}]({% ifversion not ghec%}/enterprise-cloud@latest{% endif %}/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users){% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
|
||||
Unless you're using a {% data variables.enterprise.prodname_managed_user %}, you'll still be able to access your personal account, even after leaving the organization. For more information about {% data variables.product.prodname_emus %}, see "[About {% data variables.product.prodname_emus %}]({% ifversion not ghec %}/enterprise-cloud@latest{% endif %}/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users){% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
|
||||
|
||||
## Removing professional associations with personal repositories
|
||||
|
||||
|
|
|
|||
|
|
@ -43,11 +43,11 @@ By default, the deployments page shows currently active deployments from select
|
|||
* **To view the URL for a deployment**, to the right of the commit message in the deployment history list, click {% octicon "link-external" aria-label="Navigate to deployment URL" %}.
|
||||
* **To navigate to the workflow run logs associated with a deployment**, to the right of the commit message in the deployment history list, click {% octicon "kebab-horizontal" aria-label="View logs" %}, then click **View logs**.{% ifversion deployment-dashboard-filter %}
|
||||
1. Optionally, to filter the deployment history list, create a filter.
|
||||
1. Click on the **{% octicon "filter" aria-hidden="true" %} Filter** button.
|
||||
1. Click **{% octicon "plus" aria-hidden="true" %} Add a filter**.
|
||||
1. Click on the **{% octicon "filter" aria-hidden="true" %} Filter** button.
|
||||
1. Click **{% octicon "plus" aria-hidden="true" %} Add a filter**.
|
||||
1. Choose a qualifier you would like to filter the deployment history by.
|
||||
1. Depending on the qualifier you chose, fill out information in the "Operator" and "Value" columns.
|
||||
1. Optionally, click **{% octicon "plus" aria-hidden="true" %} Add a filter** to add another filter.
|
||||
1. Optionally, click **{% octicon "plus" aria-hidden="true" %} Add a filter** to add another filter.
|
||||
1. Click **Apply**.{% endif %}
|
||||
|
||||
{% else %}
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@ The token is also available in the `github.token` context. For more information,
|
|||
|
||||
## Using the `GITHUB_TOKEN` in a workflow
|
||||
|
||||
You can use the `GITHUB_TOKEN` by using the standard syntax for referencing secrets: {%raw%}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}. Examples of using the `GITHUB_TOKEN` include passing the token as an input to an action, or using it to make an authenticated {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API request.
|
||||
You can use the `GITHUB_TOKEN` by using the standard syntax for referencing secrets: {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}. Examples of using the `GITHUB_TOKEN` include passing the token as an input to an action, or using it to make an authenticated {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API request.
|
||||
|
||||
{% note %}
|
||||
|
||||
|
|
@ -139,7 +139,7 @@ The permissions for the `GITHUB_TOKEN` are initially set to the default setting
|
|||
|
||||
### Granting additional permissions
|
||||
|
||||
If you need a token that requires permissions that aren't available in the `GITHUB_TOKEN`, you can create a {% data variables.product.prodname_github_app %} and generate an installation access token within your workflow. For more information, see "[AUTOTITLE](/apps/creating-github-apps/guides/making-authenticated-api-requests-with-a-github-app-in-a-github-actions-workflow)." Alternatively, you can create a {% data variables.product.pat_generic %}, store it as a secret in your repository, and use the token in your workflow with the {%raw%}`${{ secrets.SECRET_NAME }}`{% endraw %} syntax. For more information, see "[AUTOTITLE](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)" and "[AUTOTITLE](/actions/security-guides/using-secrets-in-github-actions)."
|
||||
If you need a token that requires permissions that aren't available in the `GITHUB_TOKEN`, you can create a {% data variables.product.prodname_github_app %} and generate an installation access token within your workflow. For more information, see "[AUTOTITLE](/apps/creating-github-apps/guides/making-authenticated-api-requests-with-a-github-app-in-a-github-actions-workflow)." Alternatively, you can create a {% data variables.product.pat_generic %}, store it as a secret in your repository, and use the token in your workflow with the {% raw %}`${{ secrets.SECRET_NAME }}`{% endraw %} syntax. For more information, see "[AUTOTITLE](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)" and "[AUTOTITLE](/actions/security-guides/using-secrets-in-github-actions)."
|
||||
|
||||
### Further reading
|
||||
|
||||
|
|
|
|||
|
|
@ -155,7 +155,7 @@ With this approach, the value of the {% raw %}`${{ github.event.issue.title }}`{
|
|||
### Using workflow templates for {% data variables.product.prodname_code_scanning %}
|
||||
|
||||
{% data reusables.advanced-security.starter-workflows-beta %}
|
||||
{% data variables.product.prodname_code_scanning_caps %} allows you to find security vulnerabilities before they reach production. {% data variables.product.product_name %} provides workflow templates for {% data variables.product.prodname_code_scanning %}. You can use these suggested workflows to construct your {% data variables.product.prodname_code_scanning %} workflows, instead of starting from scratch. {% data variables.product.company_short%}'s workflow, the {% data variables.code-scanning.codeql_workflow %}, is powered by {% data variables.product.prodname_codeql %}. There are also third-party workflow templates available.
|
||||
{% data variables.product.prodname_code_scanning_caps %} allows you to find security vulnerabilities before they reach production. {% data variables.product.product_name %} provides workflow templates for {% data variables.product.prodname_code_scanning %}. You can use these suggested workflows to construct your {% data variables.product.prodname_code_scanning %} workflows, instead of starting from scratch. {% data variables.product.company_short %}'s workflow, the {% data variables.code-scanning.codeql_workflow %}, is powered by {% data variables.product.prodname_codeql %}. There are also third-party workflow templates available.
|
||||
|
||||
For more information, see "[AUTOTITLE](/code-security/code-scanning/introduction-to-code-scanning/about-code-scanning)" and "[AUTOTITLE](/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/configuring-advanced-setup-for-code-scanning#configuring-code-scanning-using-third-party-actions)."
|
||||
|
||||
|
|
|
|||
|
|
@ -55,7 +55,7 @@ To support the developer process in the next section, add two {% data variables.
|
|||
|
||||
### Example developer process
|
||||
|
||||
Here is an example process that you can follow to automatically run tests, create a release{% ifversion fpt or ghec%} and publish to {% data variables.product.prodname_marketplace %}{% endif %}, and publish your action.
|
||||
Here is an example process that you can follow to automatically run tests, create a release{% ifversion fpt or ghec %} and publish to {% data variables.product.prodname_marketplace %}{% endif %}, and publish your action.
|
||||
|
||||
1. Do feature work in branches per GitHub flow. For more information, see "[AUTOTITLE](/get-started/using-github/github-flow)."
|
||||
* Whenever a commit is pushed to the feature branch, your testing workflow will automatically run the tests.
|
||||
|
|
|
|||
|
|
@ -228,7 +228,7 @@ You can call multiple workflows, referencing each in a separate job.
|
|||
|
||||
### Passing inputs and secrets to a reusable workflow
|
||||
|
||||
{% data reusables.actions.pass-inputs-to-reusable-workflows%}
|
||||
{% data reusables.actions.pass-inputs-to-reusable-workflows %}
|
||||
|
||||
{% ifversion actions-reusable-workflow-matrix %}
|
||||
|
||||
|
|
|
|||
|
|
@ -378,7 +378,7 @@ on:
|
|||
types: [created, deleted]
|
||||
```
|
||||
|
||||
{% ifversion merge-queue %}
|
||||
{% ifversion merge-queue %}
|
||||
|
||||
## `merge_group`
|
||||
|
||||
|
|
|
|||
|
|
@ -34,7 +34,7 @@ You can enforce policies to control the security settings for organizations owne
|
|||
{% data reusables.two_fa.mandatory-2fa-contributors-2023 %}
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghes%}If {% data variables.location.product_location %} uses LDAP or built-in authentication, enterprise{% else %}Enterprise{% endif %} owners can require that organization members, billing managers, and outside collaborators in all organizations owned by an enterprise use two-factor authentication to secure their user accounts.{% ifversion ghec %} This policy is not available for enterprises with managed users.{% endif %}
|
||||
{% ifversion ghes %}If {% data variables.location.product_location %} uses LDAP or built-in authentication, enterprise{% else %}Enterprise{% endif %} owners can require that organization members, billing managers, and outside collaborators in all organizations owned by an enterprise use two-factor authentication to secure their user accounts.{% ifversion ghec %} This policy is not available for enterprises with managed users.{% endif %}
|
||||
|
||||
Before you can require 2FA for all organizations owned by your enterprise, you must enable two-factor authentication for your own account. For more information, see "[AUTOTITLE](/authentication/securing-your-account-with-two-factor-authentication-2fa)."
|
||||
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ Restoring a repository will not restore release attachments or team permissions.
|
|||
{% data reusables.enterprise_site_admin_settings.access-settings %}
|
||||
{% data reusables.enterprise_site_admin_settings.search-user-or-org %}
|
||||
{% data reusables.enterprise_site_admin_settings.click-user-or-org %}
|
||||
1. In the {% octicon "repo" aria-hidden="true" %} **Repositories** section, click the {% octicon "trash" aria-hidden="true" %} **Deleted repositories** link.
|
||||
1. In the {% octicon "repo" aria-hidden="true" %} **Repositories** section, click the {% octicon "trash" aria-hidden="true" %} **Deleted repositories** link.
|
||||
1. Find the repository you want to restore in the deleted repositories list, then to the right of the repository name click **Restore**.
|
||||
1. To confirm you would like to restore the named repository, click **Restore**.
|
||||
|
||||
|
|
|
|||
|
|
@ -60,7 +60,7 @@ You can configure additional policies to restrict the actions available to {% if
|
|||
|
||||
## 2. Deploy the self-hosted runner for your enterprise
|
||||
|
||||
Next, add a self-hosted runner to your enterprise. {% data variables.product.product_name %} will guide you through installation of the necessary software on the runner machine. After you deploy the runner, you can verify connectivity between the runner machine and {%ifversion ghec %}your enterprise{% elsif ghes %}{% data variables.location.product_location %}{% endif %}.
|
||||
Next, add a self-hosted runner to your enterprise. {% data variables.product.product_name %} will guide you through installation of the necessary software on the runner machine. After you deploy the runner, you can verify connectivity between the runner machine and {% ifversion ghec %}your enterprise{% elsif ghes %}{% data variables.location.product_location %}{% endif %}.
|
||||
|
||||
### Adding the self-hosted runner
|
||||
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ Alternatively, if you want stricter control over which actions are allowed in yo
|
|||
|
||||
{% data reusables.actions.github-connect-resolution %}
|
||||
|
||||
If a user has already created an organization and repository in your enterprise that matches an organization and repository name on {% data variables.product.prodname_dotcom_the_website %}, the repository on your enterprise will be used instead of the {% data variables.product.prodname_dotcom_the_website %} repository. For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)."
|
||||
If a user has already created an organization and repository in your enterprise that matches an organization and repository name on {% data variables.product.prodname_dotcom_the_website %}, the repository on your enterprise will be used instead of the {% data variables.product.prodname_dotcom_the_website %} repository. For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website %}](#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)."
|
||||
|
||||
## Enabling automatic access to public {% data variables.product.prodname_dotcom_the_website %} actions
|
||||
|
||||
|
|
@ -45,7 +45,7 @@ Before enabling access to public actions from {% data variables.product.prodname
|
|||
|
||||
## Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website %}
|
||||
|
||||
When you enable {% data variables.product.prodname_github_connect %}, users see no change in behavior for existing workflows because {% data variables.product.prodname_actions %} searches {% data variables.location.product_location %} for each action before falling back to {% data variables.product.prodname_dotcom_the_website%}. This ensures that any custom versions of actions your enterprise has created are used in preference to their counterparts on {% data variables.product.prodname_dotcom_the_website%}.
|
||||
When you enable {% data variables.product.prodname_github_connect %}, users see no change in behavior for existing workflows because {% data variables.product.prodname_actions %} searches {% data variables.location.product_location %} for each action before falling back to {% data variables.product.prodname_dotcom_the_website %}. This ensures that any custom versions of actions your enterprise has created are used in preference to their counterparts on {% data variables.product.prodname_dotcom_the_website %}.
|
||||
|
||||
{% data reusables.actions.namespace-retirement-ghecom %}
|
||||
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ redirect_from:
|
|||
|
||||
{% data reusables.enterprise.about-ha %} For more information, see "[AUTOTITLE](/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration)."
|
||||
|
||||
After you configure high availability, you can proactively ensure redundancy by monitoring the overall health of replication and the status of each of your instance's replica nodes. You can use command-line utilities on the instance, an overview dashboard, {% ifversion replication-management-api %}the instance's REST API, {%endif %}or a remote monitoring system such as Nagios.
|
||||
After you configure high availability, you can proactively ensure redundancy by monitoring the overall health of replication and the status of each of your instance's replica nodes. You can use command-line utilities on the instance, an overview dashboard, {% ifversion replication-management-api %}the instance's REST API, {% endif %}or a remote monitoring system such as Nagios.
|
||||
|
||||
With high availability, your instance uses several approaches to replicate data between primary and replica nodes. Database services that support a native replication mechanism, such as MySQL, replicate using the service's native mechanism. Other services, such as Git repositories, replicate using a custom mechanism developed for {% data variables.product.product_name %}, or using platform tools like rsync.
|
||||
|
||||
|
|
|
|||
|
|
@ -85,7 +85,7 @@ When businesses adopt {% data variables.product.prodname_enterprise %}, their re
|
|||
|
||||
1. Learn more about {% data variables.product.prodname_enterprise %}.
|
||||
|
||||
* "[AUTOTITLE](/enterprise-cloud@latest/admin/overview/about-github-enterprise-cloud)"{% ifversion not ghec %} in the {% data variables.product.prodname_ghe_cloud%} documentation{% endif %}
|
||||
* "[AUTOTITLE](/enterprise-cloud@latest/admin/overview/about-github-enterprise-cloud)"{% ifversion not ghec %} in the {% data variables.product.prodname_ghe_cloud %} documentation{% endif %}
|
||||
* "[AUTOTITLE]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/overview/about-github-enterprise-server){% ifversion not ghes %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% else %}."{% endif %}
|
||||
1. Set up a trial.
|
||||
|
||||
|
|
|
|||
|
|
@ -23,4 +23,4 @@ With the APIs, you can automate many administrative tasks. Some examples include
|
|||
* Collect statistics about your enterprise. For more information, see "[AUTOTITLE](/rest/enterprise-admin/admin-stats)."
|
||||
* Manage your enterprise account. For more information, see "[AUTOTITLE](/graphql/guides/managing-enterprise-accounts)."
|
||||
|
||||
For the complete documentation for the {% data variables.product.prodname_enterprise_api %}, see [{% data variables.product.prodname_dotcom %} REST API](/rest) and [{% data variables.product.prodname_dotcom%} GraphQL API](/graphql).
|
||||
For the complete documentation for the {% data variables.product.prodname_enterprise_api %}, see [{% data variables.product.prodname_dotcom %} REST API](/rest) and [{% data variables.product.prodname_dotcom %} GraphQL API](/graphql).
|
||||
|
|
|
|||
|
|
@ -32,7 +32,7 @@ You do not need to provide a payment method during the trial.
|
|||
|
||||
The trial lasts for **{% data reusables.enterprise.ghec-trial-length %} days** and includes the following features.
|
||||
|
||||
* Access to **most** {% data variables.product.prodname_ghe_cloud %} features.{% ifversion metered-ghe-ghas%}
|
||||
* Access to **most** {% data variables.product.prodname_ghe_cloud %} features.{% ifversion metered-ghe-ghas %}
|
||||
* Access to the **new billing platform**. See "[AUTOTITLE](/billing/using-the-new-billing-platform/about-the-new-billing-platform-for-enterprises)."{% endif %}
|
||||
* An **enterprise account**, which allows you to manage multiple organizations. See "[AUTOTITLE](/enterprise-cloud@latest/get-started/learning-about-github/types-of-github-accounts)."
|
||||
* Up to **50 seats** to grant access to users.
|
||||
|
|
@ -68,7 +68,7 @@ You can end your trial at any time by purchasing {% data variables.product.prodn
|
|||
|
||||
If you **purchase {% data variables.product.prodname_enterprise %}**:
|
||||
|
||||
{% ifversion metered-ghe-ghas%}
|
||||
{% ifversion metered-ghe-ghas %}
|
||||
* You can use usage-based billing for {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_GH_advanced_security %}, which means you pay monthly for the number of licenses you use. You will not need to buy a predefined number of licenses in advance. See, "[AUTOTITLE](/billing/using-the-new-billing-platform/about-usage-based-billing-for-licenses)."
|
||||
|
||||
If you did not set up a free trial and you want to use usage-based billing to pay for {% data variables.product.prodname_GH_advanced_security %} after the {% data variables.product.prodname_ghe_cloud %} trial ends, contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).{% endif %}
|
||||
|
|
|
|||
|
|
@ -20,13 +20,13 @@ Some authenticators allow passkeys to be used with nearby devices. For example,
|
|||
|
||||
## Signing in with a passkey linked to your primary device
|
||||
|
||||
1. Navigate to the login page for {% data variables.product.prodname_dotcom %} at {% ifversion fpt or ghec%}[https://github.com/login?passkey=true](https://github.com/login?passkey=true){% else %}`https://HOSTNAME/login?passkey=true`{% endif %}.
|
||||
1. Navigate to the login page for {% data variables.product.prodname_dotcom %} at {% ifversion fpt or ghec %}[https://github.com/login?passkey=true](https://github.com/login?passkey=true){% else %}`https://HOSTNAME/login?passkey=true`{% endif %}.
|
||||
1. Click **{% octicon "passkey-fill" aria-hidden="true" %} Sign in with a passkey**.
|
||||
1. Follow the prompts on your browser or platform to select a passkey that is accessible from the device you are using, and complete the authentication process. For example, when prompted, you might touch a fingerprint sensor or enter your PIN.
|
||||
|
||||
## Signing in with a passkey using a nearby device
|
||||
|
||||
1. Navigate to the login page for {% data variables.product.prodname_dotcom %} at {% ifversion fpt or ghec%}[https://github.com/login?passkey=true](https://github.com/login?passkey=true){% else %}`https://HOSTNAME/login?passkey=true`{% endif %}.
|
||||
1. Navigate to the login page for {% data variables.product.prodname_dotcom %} at {% ifversion fpt or ghec %}[https://github.com/login?passkey=true](https://github.com/login?passkey=true){% else %}`https://HOSTNAME/login?passkey=true`{% endif %}.
|
||||
1. Click **{% octicon "passkey-fill" aria-hidden="true" %} Sign in with a passkey**.
|
||||
1. Follow the prompts on your browser or platform to select a passkey that is accessible as a nearby device (such as a phone or a tablet).
|
||||
1. Continue to follow the prompts to start the authentication process. For example, you might choose to scan a QR code, or trigger a push notification to the nearby device.
|
||||
|
|
|
|||
|
|
@ -32,7 +32,7 @@ You can change the time-based one-time password (TOTP) application you use to ge
|
|||
{% data reusables.user-settings.security %}
|
||||
{% data reusables.two_fa.edit-existing-method %}
|
||||
{% data reusables.two_fa.enable-totp-app-method %}
|
||||
{% data reusables.two_fa.save-2fa-method-when-editing%}
|
||||
{% data reusables.two_fa.save-2fa-method-when-editing %}
|
||||
|
||||
{% warning %}
|
||||
|
||||
|
|
@ -52,7 +52,7 @@ You can change the phone number you use to receive authentication codes via SMS.
|
|||
{% data reusables.user-settings.security %}
|
||||
{% data reusables.two_fa.edit-existing-method %}
|
||||
{% data reusables.two_fa.enable-sms-number-method %}
|
||||
{% data reusables.two_fa.save-2fa-method-when-editing%}
|
||||
{% data reusables.two_fa.save-2fa-method-when-editing %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
|
@ -73,7 +73,7 @@ You can add a time-based one-time password (TOTP) application to generate authen
|
|||
{% data reusables.user-settings.security %}
|
||||
{% data reusables.two_fa.add-additional-method %}
|
||||
{% data reusables.two_fa.enable-totp-app-method %}
|
||||
{% data reusables.two_fa.save-2fa-method-when-editing%}
|
||||
{% data reusables.two_fa.save-2fa-method-when-editing %}
|
||||
{% data reusables.two_fa.manual-totp-app-setup %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
|
@ -86,7 +86,7 @@ You can add a time-based one-time password (TOTP) application to generate authen
|
|||
{% data reusables.user-settings.security %}
|
||||
{% data reusables.two_fa.add-additional-method %}
|
||||
{% data reusables.two_fa.enable-sms-number-method %}
|
||||
{% data reusables.two_fa.save-2fa-method-when-editing%}
|
||||
{% data reusables.two_fa.save-2fa-method-when-editing %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
|
|
|||
|
|
@ -33,7 +33,7 @@ shortTitle: Billing for GitHub Actions
|
|||
|
||||
{% data reusables.actions.actions-spending-limit-brief %} For more information, see "[About spending limits](#about-spending-limits)."
|
||||
|
||||
If you are an organization owner{% ifversion ghec %} or enterprise owner{% endif%}, you can connect an Azure Subscription ID to your organization {% ifversion ghec %}or enterprise{% endif%} account to enable and pay for {% data variables.product.prodname_actions %} usage beyond the amounts included with your account. For more information, see "[AUTOTITLE](/billing/managing-the-plan-for-your-github-account/connecting-an-azure-subscription)."
|
||||
If you are an organization owner{% ifversion ghec %} or enterprise owner{% endif %}, you can connect an Azure Subscription ID to your organization {% ifversion ghec %}or enterprise{% endif %} account to enable and pay for {% data variables.product.prodname_actions %} usage beyond the amounts included with your account. For more information, see "[AUTOTITLE](/billing/managing-the-plan-for-your-github-account/connecting-an-azure-subscription)."
|
||||
|
||||
Minutes reset every month, while storage usage does not.
|
||||
|
||||
|
|
|
|||
|
|
@ -32,7 +32,7 @@ shortTitle: Spending limits for Actions
|
|||
|
||||
{% data reusables.actions.actions-packages-set-spending-limit %} For more information about pricing for {% data variables.product.prodname_actions %} usage, see "[AUTOTITLE](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)."
|
||||
|
||||
If you are an organization owner{% ifversion ghec %} or enterprise owner{% endif%}, you can connect an Azure Subscription ID to your organization {% ifversion ghec %}or enterprise{% endif%} account to enable and pay for {% data variables.product.prodname_actions %} usage beyond the amounts including with your account. For more information, see "[AUTOTITLE](/billing/managing-the-plan-for-your-github-account/connecting-an-azure-subscription)."
|
||||
If you are an organization owner{% ifversion ghec %} or enterprise owner{% endif %}, you can connect an Azure Subscription ID to your organization {% ifversion ghec %}or enterprise{% endif %} account to enable and pay for {% data variables.product.prodname_actions %} usage beyond the amounts including with your account. For more information, see "[AUTOTITLE](/billing/managing-the-plan-for-your-github-account/connecting-an-azure-subscription)."
|
||||
|
||||
As soon as you set a spending limit other than $0, you will be responsible for any existing overages in the current billing period. For example, if your organization uses {% data variables.product.prodname_team %}, does not allow overages, and creates workflow artifacts that increase your storage usage for the month from 1.9GB to 2.1GB, you will use slightly more storage than the 2GB your product includes.
|
||||
|
||||
|
|
|
|||
|
|
@ -47,7 +47,7 @@ To set up a trial of {% data variables.product.prodname_GH_advanced_security %},
|
|||
|
||||
You can finish your trial at any time by purchasing {% data variables.product.prodname_GH_advanced_security %}. If you haven't purchased {% data variables.product.prodname_GH_advanced_security %} by the end of the 30 days, your trial will expire.
|
||||
|
||||
{% ifversion metered-ghe-ghas%}
|
||||
{% ifversion metered-ghe-ghas %}
|
||||
|
||||
If you pay for {% data variables.product.prodname_ghe_cloud %} with usage-based billing, but did not set up a free trial of {% data variables.product.prodname_GH_advanced_security %}, you can still use usage-based billing to pay for {% data variables.product.prodname_GH_advanced_security %} after the {% data variables.product.prodname_ghe_cloud %} trial ends. For more information, contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
|
||||
|
||||
|
|
|
|||
|
|
@ -118,7 +118,7 @@ If you enable prebuilding of codespaces this will incur additional charges. See
|
|||
|
||||
Billing for {% data variables.product.prodname_github_codespaces %} shares your account's existing payment method, and receipt. See "[AUTOTITLE](/billing/managing-your-github-billing-settings/viewing-your-subscriptions-and-billing-date)."
|
||||
|
||||
If you are an organization owner{% ifversion ghec %} or enterprise owner{% endif%}, you can connect an Azure Subscription ID to your organization {% ifversion ghec %}or enterprise{% endif%} account to enable and pay for {% data variables.product.prodname_github_codespaces %} usage. See "[AUTOTITLE](/billing/managing-the-plan-for-your-github-account/connecting-an-azure-subscription)."
|
||||
If you are an organization owner{% ifversion ghec %} or enterprise owner{% endif %}, you can connect an Azure Subscription ID to your organization {% ifversion ghec %}or enterprise{% endif %} account to enable and pay for {% data variables.product.prodname_github_codespaces %} usage. See "[AUTOTITLE](/billing/managing-the-plan-for-your-github-account/connecting-an-azure-subscription)."
|
||||
|
||||
## About billing for compute usage
|
||||
|
||||
|
|
|
|||
|
|
@ -35,7 +35,7 @@ Once you've reached your spending limit, you will no longer be able to create ne
|
|||
|
||||
## Using your Azure Subscription
|
||||
|
||||
If you are an organization owner{% ifversion ghec %} or enterprise owner{% endif%}, you can connect an Azure Subscription ID to your organization {% ifversion ghec %}or enterprise{% endif%} account to enable and pay for {% data variables.product.prodname_github_codespaces %} usage. See "[AUTOTITLE](/billing/managing-the-plan-for-your-github-account/connecting-an-azure-subscription)."
|
||||
If you are an organization owner{% ifversion ghec %} or enterprise owner{% endif %}, you can connect an Azure Subscription ID to your organization {% ifversion ghec %}or enterprise{% endif %} account to enable and pay for {% data variables.product.prodname_github_codespaces %} usage. See "[AUTOTITLE](/billing/managing-the-plan-for-your-github-account/connecting-an-azure-subscription)."
|
||||
|
||||
## Managing the {% data variables.product.prodname_github_codespaces %} spending limit for your personal account
|
||||
|
||||
|
|
|
|||
|
|
@ -40,7 +40,7 @@ shortTitle: About billing
|
|||
|
||||
{% endnote %}
|
||||
|
||||
If you are an organization owner{% ifversion ghec %} or enterprise owner{% endif%}, you can connect an Azure Subscription ID to your organization {% ifversion ghec %}or enterprise{% endif%} account to enable and pay for {% data variables.product.prodname_registry %} usage beyond the amounts including with your account. For more information, see "[AUTOTITLE](/billing/managing-the-plan-for-your-github-account/connecting-an-azure-subscription)."
|
||||
If you are an organization owner{% ifversion ghec %} or enterprise owner{% endif %}, you can connect an Azure Subscription ID to your organization {% ifversion ghec %}or enterprise{% endif %} account to enable and pay for {% data variables.product.prodname_registry %} usage beyond the amounts including with your account. For more information, see "[AUTOTITLE](/billing/managing-the-plan-for-your-github-account/connecting-an-azure-subscription)."
|
||||
|
||||
Data transfer resets every month, while storage usage does not.
|
||||
|
||||
|
|
|
|||
|
|
@ -33,7 +33,7 @@ shortTitle: Your spending limit
|
|||
|
||||
{% data reusables.actions.actions-packages-set-spending-limit %} For more information about pricing for {% data variables.product.prodname_registry %} usage, see "[AUTOTITLE](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)."
|
||||
|
||||
If you are an organization owner{% ifversion ghec %} or enterprise owner{% endif%}, you can connect an Azure Subscription ID to your organization {% ifversion ghec %}or enterprise{% endif%} account to enable and pay for {% data variables.product.prodname_registry %} usage beyond the amounts including with your account. For more information, see "[AUTOTITLE](/billing/managing-the-plan-for-your-github-account/connecting-an-azure-subscription)."
|
||||
If you are an organization owner{% ifversion ghec %} or enterprise owner{% endif %}, you can connect an Azure Subscription ID to your organization {% ifversion ghec %}or enterprise{% endif %} account to enable and pay for {% data variables.product.prodname_registry %} usage beyond the amounts including with your account. For more information, see "[AUTOTITLE](/billing/managing-the-plan-for-your-github-account/connecting-an-azure-subscription)."
|
||||
|
||||
As soon as you set a spending limit other than $0, you will be responsible for any existing overages in the current billing period. For example, if your organization uses {% data variables.product.prodname_team %}, does not allow overages, and publishes a new version of a private package that increases your storage usage for the month from 1.9GB to 2.1GB, publishing the version will use slightly more than the 2GB your product includes.
|
||||
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ shortTitle: Connect an Azure subscription
|
|||
|
||||
## About connection of an Azure subscription
|
||||
|
||||
You can pay for usage of {% data variables.product.product_name %} features through Azure by connecting an Azure Subscription ID to your organization {% ifversion ghec %}or enterprise{% endif%} account on {% data variables.location.product_location %}. {% ifversion fpt %}For more information about organization accounts, see "[AUTOTITLE](/organizations/collaborating-with-groups-in-organizations/about-organizations)."{% elsif ghec %}
|
||||
You can pay for usage of {% data variables.product.product_name %} features through Azure by connecting an Azure Subscription ID to your organization {% ifversion ghec %}or enterprise{% endif %} account on {% data variables.location.product_location %}. {% ifversion fpt %}For more information about organization accounts, see "[AUTOTITLE](/organizations/collaborating-with-groups-in-organizations/about-organizations)."{% elsif ghec %}
|
||||
|
||||
In this article, the instructions that you must follow to connect an Azure subscription depend on whether your company uses a single organization or an enterprise account on {% data variables.location.product_location %}. For more information about the differences between these two types of accounts, see "[AUTOTITLE](/get-started/learning-about-github/types-of-github-accounts)."{% endif %}
|
||||
|
||||
|
|
@ -56,7 +56,7 @@ If you use {% data variables.product.product_name %} through a Microsoft Enterpr
|
|||
|
||||
If you link your {% data variables.product.company_short %} account to Azure, any usage-based costs starting from that point will be billed through Azure and charged on the 1st of each month. However, remaining {% data variables.product.company_short %} charges, for example charges for your {% data variables.product.prodname_dotcom %} plan, will still be billed on your usual billing date.
|
||||
|
||||
For example, you link your Azure subscription to your organization {% ifversion ghec %}or enterprise{% endif%} account on June 16th and you also have a {% data variables.product.prodname_copilot_for_business %} subscription. From that date onwards, any usage costs for {% data variables.product.prodname_copilot_business_short %} will be included in your Azure bill and charged on July 1st. However, any charges incurred before June 16th for {% data variables.product.prodname_copilot_business_short %} will be billed separately through {% data variables.product.company_short %} on your account's usual billing date.
|
||||
For example, you link your Azure subscription to your organization {% ifversion ghec %}or enterprise{% endif %} account on June 16th and you also have a {% data variables.product.prodname_copilot_for_business %} subscription. From that date onwards, any usage costs for {% data variables.product.prodname_copilot_business_short %} will be included in your Azure bill and charged on July 1st. However, any charges incurred before June 16th for {% data variables.product.prodname_copilot_business_short %} will be billed separately through {% data variables.product.company_short %} on your account's usual billing date.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ The following products are available in the new billing platform:
|
|||
* {% data variables.product.prodname_registry %}
|
||||
* {% data variables.large_files.product_name_long %}
|
||||
|
||||
{% ifversion metered-ghe-ghas%}
|
||||
{% ifversion metered-ghe-ghas %}
|
||||
|
||||
{% data reusables.billing.actions-usage-delay %}
|
||||
|
||||
|
|
|
|||
|
|
@ -31,7 +31,7 @@ On this page, you can view your usage in the following categories:
|
|||
* **By organization** and **by repository:** The two cards under the graph show the top five organizations and repositories that generate the most usage. You can click {% octicon "kebab-horizontal" aria-label="Open column options" %} in the upper-right corner of each card to view all usage.
|
||||
* **By products:** You can use the product tabs to view usage and discounts for different products. Only products with usage are shown.
|
||||
|
||||
{% ifversion metered-ghe-ghas%}
|
||||
{% ifversion metered-ghe-ghas %}
|
||||
|
||||
{% data reusables.billing.actions-usage-delay %}
|
||||
|
||||
|
|
|
|||
|
|
@ -84,7 +84,7 @@ Through the "Code security and analysis" page of your organization's settings, y
|
|||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.security-and-analysis %}
|
||||
1. Click **Enable all** next to "{% data variables.product.prodname_code_scanning_caps %}".{% ifversion bulk-code-scanning-query-suite%}
|
||||
1. Click **Enable all** next to "{% data variables.product.prodname_code_scanning_caps %}".{% ifversion bulk-code-scanning-query-suite %}
|
||||
1. In the "Query suites" section of the "Enable {% data variables.product.prodname_code_scanning %} default setup" dialog box displayed, select the query suite your configuration of default setup will run. For more information, see "[AUTOTITLE](/code-security/code-scanning/managing-your-code-scanning-configuration/codeql-query-suites)."
|
||||
1. To enable your configuration of default setup, click **Enable for eligible repositories**.
|
||||
1. Optionally, to recommend the "Extended" query suite throughout your organization when enabling default setup, select "Recommend the extended query suite for repositories enabling default setup."{% else %}
|
||||
|
|
|
|||
|
|
@ -50,7 +50,7 @@ To use {% data variables.product.prodname_code_scanning %} on a private reposito
|
|||
|
||||
## About tools for {% data variables.product.prodname_code_scanning %}
|
||||
|
||||
You can configure {% data variables.product.prodname_code_scanning %} to use the {% data variables.product.prodname_codeql %} product maintained by {% data variables.product.company_short%} or a third-party {% data variables.product.prodname_code_scanning %} tool.
|
||||
You can configure {% data variables.product.prodname_code_scanning %} to use the {% data variables.product.prodname_codeql %} product maintained by {% data variables.product.company_short %} or a third-party {% data variables.product.prodname_code_scanning %} tool.
|
||||
|
||||
### About {% data variables.product.prodname_codeql %} analysis
|
||||
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@ With a {% data variables.product.prodname_copilot_enterprise %} license, you can
|
|||
{% data reusables.repositories.sidebar-security %}
|
||||
{% data reusables.repositories.sidebar-code-scanning-alerts %}
|
||||
1. Click the name of an alert.
|
||||
1. If {% data variables.product.prodname_copilot_autofix_short %} can suggest a fix, at the top of the page, click **{% octicon "shield-check" aria-label="Generate fix"%} Generate fix**.
|
||||
1. If {% data variables.product.prodname_copilot_autofix_short %} can suggest a fix, at the top of the page, click **{% octicon "shield-check" aria-label="Generate fix" %} Generate fix**.
|
||||
1. Once the suggested fix has been generated, at the bottom of the page, you can click **Create PR with fix** to automatically generate a pull request with the suggested fix.
|
||||
A new branch is created from the default branch, the generated fix is committed and a draft pull request is created. You can test and edit the suggested fix as you would with any other fix.
|
||||
|
||||
|
|
|
|||
|
|
@ -92,13 +92,13 @@ You can download the list of rules that {% data variables.product.prodname_code_
|
|||
* The SARIF identifier.
|
||||
* How many alerts were found.
|
||||
|
||||
To download a report, select a configuration you're interested in. Then click **{% octicon "kebab-horizontal" aria-label="Configuration menu" %}** on the top right of the page, and select **{% octicon "download" aria-hidden="true" %} Download list of rules used**.
|
||||
To download a report, select a configuration you're interested in. Then click **{% octicon "kebab-horizontal" aria-label="Configuration menu" %}** on the top right of the page, and select **{% octicon "download" aria-hidden="true" %} Download list of rules used**.
|
||||
|
||||
### Removing configurations
|
||||
|
||||
You can remove stale, duplicate, or unwanted configurations for the default branch of your repository.
|
||||
|
||||
To remove a configuration, select the configuration you want to delete. Then click **{% octicon "kebab-horizontal" aria-label="Configuration menu" %}** on the top right of the page, and select **{% octicon "trash" aria-hidden="true" %} Delete configuration**. Once you have read the warning about alerts, to confirm the deletion, click the **Delete** button.
|
||||
To remove a configuration, select the configuration you want to delete. Then click **{% octicon "kebab-horizontal" aria-label="Configuration menu" %}** on the top right of the page, and select **{% octicon "trash" aria-hidden="true" %} Delete configuration**. Once you have read the warning about alerts, to confirm the deletion, click the **Delete** button.
|
||||
|
||||
{% note %}
|
||||
|
||||
|
|
|
|||
|
|
@ -175,7 +175,7 @@ You can add a maximum of 1,000 repositories to a custom list per search.
|
|||
|
||||
1. In the "Variant Analysis Repositories" view, choose the list that you want to add repositories to. You can create a new list or choose an existing list that already contains repositories.
|
||||
|
||||
1. Right-click on the list you have chosen and then click **Add repositories with {% data variables.product.prodname_dotcom%} code search**.
|
||||
1. Right-click on the list you have chosen and then click **Add repositories with {% data variables.product.prodname_dotcom %} code search**.
|
||||
|
||||
1. In the pop-up that appears at the top of the application, under the search bar, select a language for your search from the choices in the dropdown.
|
||||
|
||||
|
|
|
|||
|
|
@ -124,7 +124,7 @@ You can enable or disable {% data variables.product.prodname_dependabot_alerts %
|
|||
|
||||
**Note:** When {% data variables.product.prodname_dependabot_alerts %} are enabled or disabled at the enterprise level, it overrides the organization and repository level settings for {% data variables.product.prodname_dependabot_alerts %}.
|
||||
|
||||
{% endnote%}
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
|
||||
{% ifversion dependabot-alerts-enterprise-enablement or ghes %}
|
||||
|
|
|
|||
|
|
@ -82,7 +82,7 @@ If you're not sure about the impact a feature will have, you may want to test th
|
|||
{% data reusables.organizations.navigate-to-org %}
|
||||
{% data reusables.organizations.security-overview %}
|
||||
|
||||
1. In the sidebar, click **{% octicon "meter" aria-hidden="true" %} Coverage**.
|
||||
1. In the sidebar, click **{% octicon "meter" aria-hidden="true" %} Coverage**.
|
||||
|
||||
On this view, you can use checkboxes to select specific repositories, or you can use the search bar to find the repositories where you want to enable a feature. For example, you can use filters to identify repositories where a certain team has write or admin access, or exclude repositories that don't require the same level of protection, such as test repositories or repositories for internal documentation. Then you can enable features for all selected repositories at once. For more information, see "[AUTOTITLE](/code-security/security-overview/enabling-security-features-for-multiple-repositories)."
|
||||
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ When you save a change to a custom pattern, this closes all the {% data variable
|
|||
|
||||
{% data reusables.secret-scanning.view-custom-pattern %}
|
||||
1. Under "{% data variables.product.prodname_secret_scanning_caps %}", to the right of the custom pattern you want to edit, click {% octicon "pencil" aria-label="Edit pattern" %}.
|
||||
{%- ifversion custom-pattern-dry-run-ga %}
|
||||
{%- ifversion custom-pattern-dry-run-ga %}
|
||||
1. When you're ready to test your edited custom pattern, to identify matches without creating alerts, click **Save and dry run**.
|
||||
{%- endif %}
|
||||
1. When you have reviewed and tested your changes, click **Publish changes**.{% ifversion secret-scanning-push-protection-custom-patterns %}
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ For more information about non-provider patterns, see "{% ifversion fpt or ghec
|
|||
|
||||
### Enabling detection of non-provider patterns for a repository
|
||||
|
||||
{%endif %}
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@ The campaign templates contain filters for the most common alert selections. {%
|
|||
|
||||
{% data reusables.organizations.navigate-to-org %}
|
||||
{% data reusables.organizations.security-overview %}
|
||||
1. In the left sidebar, next to "Campaigns", click the {% octicon "plus" aria-label="New campaign" %} icon to start creating a campaign.
|
||||
1. In the left sidebar, next to "Campaigns", click the {% octicon "plus" aria-label="New campaign" %} icon to start creating a campaign.
|
||||
1. Select one of the pre-defined filter templates to open a "New campaign from TEMPLATE_NAME template" dialog box.
|
||||
1. If the message "This looks like a big campaign" is displayed, click **Back to filters** to display the {% data variables.product.prodname_code_scanning %} alerts view with the campaign template filter shown.
|
||||
1. Add further filters to reduce the number of alerts shown, for example, filtering by "Team" or by custom property.
|
||||
|
|
|
|||
|
|
@ -41,7 +41,7 @@ You can view data to assess the enablement of code security features across repo
|
|||
|
||||
{% data reusables.organizations.navigate-to-org %}
|
||||
{% data reusables.organizations.security-overview %}
|
||||
1. To display the "Security coverage" view, in the sidebar, click **{% octicon "meter" aria-hidden="true" %} Coverage**.
|
||||
1. To display the "Security coverage" view, in the sidebar, click **{% octicon "meter" aria-hidden="true" %} Coverage**.
|
||||
{% data reusables.code-scanning.using-security-overview-coverage %}
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -35,7 +35,7 @@ The CSV file you download will contain data corresponding to the filters you hav
|
|||
{% data reusables.profile.access_org %}
|
||||
1. In the "Organizations" section, select the organization for which you would like to download security overview data.
|
||||
{% data reusables.organizations.security-overview %}
|
||||
1. In the "Security" sidebar, choose the page that you want to export data from by clicking on **{% octicon "graph" aria-hidden="true" %}Overview**, **{% octicon "meter" aria-hidden="true" %} Coverage**, **{% octicon "shield" aria-hidden="true" %} Risk** or **{% octicon "graph" aria-hidden="true" %} {% data variables.product.prodname_codeql %} pull request alerts**.
|
||||
1. In the "Security" sidebar, choose the page that you want to export data from by clicking on **{% octicon "graph" aria-hidden="true" %}Overview**, **{% octicon "meter" aria-hidden="true" %} Coverage**, **{% octicon "shield" aria-hidden="true" %} Risk** or **{% octicon "graph" aria-hidden="true" %} {% data variables.product.prodname_codeql %} pull request alerts**.
|
||||
1. Next to the search bar, click {% octicon "download" aria-hidden="true" %} **Export CSV**.
|
||||
|
||||
It may take a moment for {% data variables.product.product_name %} to generate the CSV file of your data. Once the CSV file generates, the file will automatically start downloading, and a banner will appear confirming your report is ready. If you are downloading the CSV from the overview page, you will also receive an email when your report is ready, containing a link to download the CSV.
|
||||
|
|
|
|||
|
|
@ -160,7 +160,7 @@ The level of risk for a repository is determined by the number and severity of a
|
|||
|
||||
You can filter the "Overview" view by the type{% ifversion security-overview-3-14-overview %} and property{% endif %} of alerts. Use the `tool` qualifier to display only data for alerts generated by a specific tool{% ifversion security-overview-3-14-overview %} or type of tool{% endif %}.
|
||||
|
||||
* `tool:codeql` to show data only for {% data variables.product.prodname_code_scanning %} alerts generated using {% data variables.product.prodname_codeql%}.
|
||||
* `tool:codeql` to show data only for {% data variables.product.prodname_code_scanning %} alerts generated using {% data variables.product.prodname_codeql %}.
|
||||
* `tool:dependabot` to show data only for {% data variables.product.prodname_dependabot_alerts %}.
|
||||
* `tool:secret-scanning` to show data only for {% data variables.secret-scanning.alerts %}.{% ifversion security-overview-3-14-overview %}
|
||||
* `tool:github` or `tool:third-party` to show data for all types of alerts generated by {% data variables.product.prodname_dotcom %} tools or by third-party tools.
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ For more information, see "[AUTOTITLE](/code-security/secret-scanning/using-adva
|
|||
|
||||
{% data reusables.organizations.navigate-to-org %}
|
||||
{% data reusables.organizations.security-overview %}
|
||||
1. In the sidebar, under "Requests", click **{% octicon "key" aria-hidden="true" %} Push protection bypass**.
|
||||
1. In the sidebar, under "Requests", click **{% octicon "key" aria-hidden="true" %} Push protection bypass**.
|
||||
1. Select the **All statuses** dropdown menu, then click **Open** to view requests that are awaiting review, or that have been approved but for which the commits haven't been pushed to the repository yet.
|
||||
1. Click the request that you want to review.
|
||||
1. Review the details of the request.
|
||||
|
|
|
|||
|
|
@ -40,7 +40,7 @@ You can apply filters to the data. The metrics are based on activity from the de
|
|||
|
||||
{% data reusables.organizations.navigate-to-org %}
|
||||
{% data reusables.organizations.security-overview %}
|
||||
1. In the sidebar, under "Metrics", click **{% octicon "graph" aria-hidden="true" %} {% data variables.product.prodname_codeql %} pull request alerts**.
|
||||
1. In the sidebar, under "Metrics", click **{% octicon "graph" aria-hidden="true" %} {% data variables.product.prodname_codeql %} pull request alerts**.
|
||||
1. Optionally, use the date picker to set the time range. The date picker will show data based on the pull request alerts' creation dates.
|
||||
1. Optionally, apply filters in the search box at the top of the page.
|
||||
1. Alternatively, you can open the advanced filter dialog:
|
||||
|
|
|
|||
|
|
@ -55,7 +55,7 @@ The metrics are based on activity from the default period or your selected perio
|
|||
|
||||
{% data reusables.organizations.navigate-to-org %}
|
||||
{% data reusables.organizations.security-overview %}
|
||||
1. In the sidebar, under "Metrics", click **{% octicon "graph" aria-hidden="true" %} {% data variables.product.prodname_secret_scanning_caps %}**.
|
||||
1. In the sidebar, under "Metrics", click **{% octicon "graph" aria-hidden="true" %} {% data variables.product.prodname_secret_scanning_caps %}**.
|
||||
1. Click on an individual secret type or repository to see the associated {% data variables.secret-scanning.alerts %} for your organization.
|
||||
{% data reusables.security-overview.filter-secret-scanning-metrics %}
|
||||
|
||||
|
|
|
|||
|
|
@ -67,7 +67,7 @@ Keep in mind that the overview page tracks changes over time for security alert
|
|||
|
||||
{% data reusables.organizations.navigate-to-org %}
|
||||
{% data reusables.organizations.security-overview %}
|
||||
1. The overview page is the primary view that you will see after clicking on the "Security" tab. To get to the dashboard from another security overview page, in the sidebar, click **{% octicon "graph" aria-hidden="true" %} Overview**.{% ifversion security-overview-3-tab-dashboard %}
|
||||
1. The overview page is the primary view that you will see after clicking on the "Security" tab. To get to the dashboard from another security overview page, in the sidebar, click **{% octicon "graph" aria-hidden="true" %} Overview**.{% ifversion security-overview-3-tab-dashboard %}
|
||||
1. By default, the **Detection** tab is displayed. If you want to switch to another tab to see other metrics, click **Remediation** or **Prevention**.{% endif %}
|
||||
{% data reusables.security-overview.filter-and-toggle %}
|
||||
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ If it currently takes more than 2 minutes to create a codespace for a repository
|
|||
|
||||
By default, whenever you push changes to your repository, {% data variables.product.prodname_github_codespaces %} uses {% data variables.product.prodname_actions %} to automatically update your prebuilds.
|
||||
|
||||
When prebuilds are available for a particular branch of a repository, a particular dev container configuration file, and for your region, you'll see the "{% octicon "zap" aria-hidden="true" %} Prebuild ready" label in the list of machine type options when you create a codespace. If a prebuild is still being created, you will see the "{% octicon "history" aria-hidden="true" %} Prebuild in progress" label. For more information, see "[AUTOTITLE](/codespaces/developing-in-a-codespace/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)."
|
||||
When prebuilds are available for a particular branch of a repository, a particular dev container configuration file, and for your region, you'll see the "{% octicon "zap" aria-hidden="true" %} Prebuild ready" label in the list of machine type options when you create a codespace. If a prebuild is still being created, you will see the "{% octicon "history" aria-hidden="true" %} Prebuild in progress" label. For more information, see "[AUTOTITLE](/codespaces/developing-in-a-codespace/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)."
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -51,7 +51,7 @@ Both {% data variables.codespaces.serverless %} and {% data variables.product.pr
|
|||
| **Cost** | Free. | Free monthly quota of usage for personal accounts. For information on pricing, see "[AUTOTITLE](/free-pro-team@latest/billing/managing-billing-for-your-products/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#about-github-codespaces-pricing)."|
|
||||
| **Availability** | Available to everyone on GitHub.com. | Available to everyone on GitHub.com. |
|
||||
| **Start up** | {% data variables.codespaces.serverless %} opens instantly with a key-press and you can start using it right away, without having to wait for additional configuration or installation. | When you create or resume a codespace, the codespace is assigned a VM and the container is configured based on the contents of a `devcontainer.json` file. This set up may take a few minutes to create the environment. See "[AUTOTITLE](/codespaces/developing-in-a-codespace/creating-a-codespace-for-a-repository)." |
|
||||
| **Compute** | There is no associated compute, so you won’t be able to build and run your code or use the integrated terminal. | With {% data variables.product.prodname_github_codespaces %}, you get the power of a dedicated VM on which you can run and debug your application.|
|
||||
| **Compute** | There is no associated compute, so you won’t be able to build and run your code or use the integrated terminal. | With {% data variables.product.prodname_github_codespaces %}, you get the power of a dedicated VM on which you can run and debug your application.|
|
||||
| **Terminal access** | None. | {% data variables.product.prodname_github_codespaces %} provides a common set of tools by default, meaning that you can use the Terminal exactly as you would in your local environment.|
|
||||
| **Extensions** | Only a subset of extensions that can run in the web will appear in the Extensions View and can be installed. See "[Using extensions](#using-extensions)."| With {% data variables.product.prodname_github_codespaces %}, you can use most extensions from the {% data variables.product.prodname_vscode_marketplace %}.|
|
||||
|
||||
|
|
|
|||
|
|
@ -47,7 +47,7 @@ redirect_from:
|
|||
|
||||
{% data reusables.copilot.more-details-content-exclusion-logs %}
|
||||
|
||||
{% ifversion ghec%}
|
||||
{% ifversion ghec %}
|
||||
|
||||
## Reviewing changes in your enterprise
|
||||
|
||||
|
|
|
|||
|
|
@ -72,7 +72,7 @@ For more information about enabling telemetry in various IDEs, see:
|
|||
|
||||
## Further reading
|
||||
|
||||
{% ifversion ghec%}
|
||||
{% ifversion ghec %}
|
||||
* "[AUTOTITLE](/copilot/managing-copilot/managing-copilot-for-your-enterprise/viewing-copilot-usage-for-your-enterprise)"{% endif %}
|
||||
* [{% data variables.product.prodname_copilot %} Trust Center](https://resources.github.com/copilot-trust-center)
|
||||
* "[AUTOTITLE](/copilot/managing-github-copilot-in-your-organization/granting-access-to-copilot-for-members-of-your-organization)."
|
||||
|
|
|
|||
|
|
@ -33,7 +33,7 @@ You can use content exclusions to configure {% data variables.product.prodname_c
|
|||
|
||||
### Who can configure content exclusion
|
||||
|
||||
Repository administrators{% ifversion ghec%}, organization owners, and enterprise owners{% else %} and organization owners{% endif %} can configure content exclusion.
|
||||
Repository administrators{% ifversion ghec %}, organization owners, and enterprise owners{% else %} and organization owners{% endif %} can configure content exclusion.
|
||||
|
||||
{% data reusables.copilot.content-exclusions-scope %}
|
||||
|
||||
|
|
@ -65,7 +65,7 @@ You can use your repository settings to specify content in your repository that
|
|||
|
||||
1. In the "Code & automation" section of the side bar, click **{% octicon "copilot" aria-hidden="true" %} {% data variables.product.prodname_copilot_short %}**.
|
||||
|
||||
If your repository inherits any exclusions from {%ifversion fpt %}its parent organization{% else %} organizations in the same enterprise{% endif %}, you'll see {%ifversion ghec %}one or more{% else %} a{% endif %} gray box{%ifversion ghec %}es{% endif %} at the top of the page containing details of these exclusions. You cannot edit these settings.
|
||||
If your repository inherits any exclusions from {% ifversion fpt %}its parent organization{% else %} organizations in the same enterprise{% endif %}, you'll see {% ifversion ghec %}one or more{% else %} a{% endif %} gray box{% ifversion ghec %}es{% endif %} at the top of the page containing details of these exclusions. You cannot edit these settings.
|
||||
|
||||
1. In the box following "Paths to exclude in this repository," enter the paths to files from which {% data variables.product.prodname_copilot_short %} should be excluded.
|
||||
|
||||
|
|
|
|||
|
|
@ -33,7 +33,7 @@ When a file is affected by a content exclusion setting, {% data variables.produc
|
|||
|
||||
{% data reusables.copilot.content-exclusion-note %}
|
||||
|
||||
Content exclusion can be configured at the repository{% ifversion ghec%}, organization, and enterprise{% else %} and organization{% endif %} level. The scope of the exclusion is determined by the level at which the rule is set:
|
||||
Content exclusion can be configured at the repository{% ifversion ghec %}, organization, and enterprise{% else %} and organization{% endif %} level. The scope of the exclusion is determined by the level at which the rule is set:
|
||||
|
||||
{% data reusables.copilot.content-exclusions-scope %}
|
||||
|
||||
|
|
|
|||
|
|
@ -33,10 +33,10 @@ These steps describe how to view and collect the log files for the following Jet
|
|||
* RubyMine
|
||||
* WebStorm
|
||||
|
||||
The {% data variables.product.prodname_copilot%} extension logs to the IDEA log location for IntelliJ plugins.
|
||||
The {% data variables.product.prodname_copilot %} extension logs to the IDEA log location for IntelliJ plugins.
|
||||
1. In your JetBrains IDE, open the **Help** menu.
|
||||
1. Go to **Show Log in Finder**.
|
||||
1. Open the `idea.log` in your preferred editor and look for any errors related to {% data variables.product.prodname_dotcom%} or {% data variables.product.prodname_copilot%}.
|
||||
1. Open the `idea.log` in your preferred editor and look for any errors related to {% data variables.product.prodname_dotcom %} or {% data variables.product.prodname_copilot %}.
|
||||
|
||||
For more information, see the [Locating IDE log files](https://intellij-support.jetbrains.com/hc/en-us/articles/207241085-Locating-IDE-log-files) in the IntelliJ documentation.
|
||||
|
||||
|
|
@ -45,7 +45,7 @@ For more information, see the [Locating IDE log files](https://intellij-support.
|
|||
1. In Rider, open the **Help** menu.
|
||||
1. Go to **Diagnostic Tools**.
|
||||
1. Go to **Show Log in**.
|
||||
1. Open the `idea.log` in your preferred editor and look for any errors related to {% data variables.product.prodname_dotcom%} or {% data variables.product.prodname_copilot%}.
|
||||
1. Open the `idea.log` in your preferred editor and look for any errors related to {% data variables.product.prodname_dotcom %} or {% data variables.product.prodname_copilot %}.
|
||||
|
||||
## Enabling debug mode
|
||||
|
||||
|
|
@ -66,17 +66,17 @@ If you find the log file doesn't contain enough information to resolve an issue,
|
|||
|
||||
## Viewing network connectivity diagnostics logs
|
||||
|
||||
If you encounter problems connecting to {% data variables.product.prodname_copilot%} due to network restrictions, firewalls, or your proxy setup, use the following troubleshooting steps.
|
||||
If you encounter problems connecting to {% data variables.product.prodname_copilot %} due to network restrictions, firewalls, or your proxy setup, use the following troubleshooting steps.
|
||||
|
||||
1. In the menu bar, click **Tools**, select **{% data variables.product.prodname_copilot%}**, and click **Log Diagnostics**.
|
||||
1. In the menu bar, click **Tools**, select **{% data variables.product.prodname_copilot %}**, and click **Log Diagnostics**.
|
||||
1. The `idea.log` file should open in the JetBrains IDE with the diagnostics output. Alternatively, you can open the `idea.log` file in your preferred editor.
|
||||
1. Check the section on **Reachability** to determine if {% data variables.product.prodname_copilot%} can access the necessary services.
|
||||
1. Check the section on **Reachability** to determine if {% data variables.product.prodname_copilot %} can access the necessary services.
|
||||
|
||||
## Troubleshooting certificate-related errors
|
||||
|
||||
If you're using a custom certificate, ensure the certificate is installed correctly in the operating system, see "[AUTOTITLE](/copilot/troubleshooting-github-copilot/troubleshooting-network-errors-for-github-copilot)". Then use the following troubleshooting steps.
|
||||
|
||||
1. In the menu bar, click **Tools**, select **{% data variables.product.prodname_copilot%}**, and click **Log CA Certificates**.
|
||||
1. In the menu bar, click **Tools**, select **{% data variables.product.prodname_copilot %}**, and click **Log CA Certificates**.
|
||||
1. The `idea.log` file should open in the JetBrains IDE with the trusted CA certificates logged in PEM format. You may need to refresh the `idea.log` file to view all of the output. Alternatively, you can open the `idea.log` file in your preferred editor.
|
||||
1. Check to see if the expected custom certificate is included in the certificate list output.
|
||||
|
||||
|
|
@ -86,10 +86,10 @@ If you're using a custom certificate, ensure the certificate is installed correc
|
|||
|
||||
## Viewing logs in {% data variables.product.prodname_vs %}
|
||||
|
||||
The log files for the {% data variables.product.prodname_copilot%} extension are stored in the standard log location for {% data variables.product.prodname_vs %} extensions.
|
||||
The log files for the {% data variables.product.prodname_copilot %} extension are stored in the standard log location for {% data variables.product.prodname_vs %} extensions.
|
||||
1. Open the **View** menu in {% data variables.product.prodname_vs %}.
|
||||
1. Click **Output**.
|
||||
1. On the right of the Output view pane, select **{% data variables.product.prodname_copilot%}** from the dropdown menu.
|
||||
1. On the right of the Output view pane, select **{% data variables.product.prodname_copilot %}** from the dropdown menu.
|
||||
|
||||
## Further reading
|
||||
|
||||
|
|
@ -101,10 +101,10 @@ The log files for the {% data variables.product.prodname_copilot%} extension are
|
|||
|
||||
## Viewing and collecting log files
|
||||
|
||||
The log files for the {% data variables.product.prodname_copilot%} extension are stored in the standard log location for {% data variables.product.prodname_vscode %} extensions. The log files are useful for diagnosing connection issues.
|
||||
The log files for the {% data variables.product.prodname_copilot %} extension are stored in the standard log location for {% data variables.product.prodname_vscode %} extensions. The log files are useful for diagnosing connection issues.
|
||||
1. Open the **View** menu in {% data variables.product.prodname_vscode %}.
|
||||
1. Click **Output**.
|
||||
1. On the right of the Output view pane, select **{% data variables.product.prodname_copilot%}** from the dropdown menu.
|
||||
1. On the right of the Output view pane, select **{% data variables.product.prodname_copilot %}** from the dropdown menu.
|
||||
|
||||
Alternatively, you can open the log folder for {% data variables.product.prodname_vscode %} extensions in your system's file explorer. This is useful if you need to forward the log files to the support team.
|
||||
|
||||
|
|
@ -117,15 +117,15 @@ Alternatively, you can open the log folder for {% data variables.product.prodnam
|
|||
|
||||
## Viewing network connectivity diagnostics logs
|
||||
|
||||
If you encounter problems connecting to {% data variables.product.prodname_copilot%} due to network restrictions, firewalls, or your proxy setup, use the following troubleshooting steps.
|
||||
If you encounter problems connecting to {% data variables.product.prodname_copilot %} due to network restrictions, firewalls, or your proxy setup, use the following troubleshooting steps.
|
||||
|
||||
1. Open the {% data variables.product.prodname_vscode_command_palette_shortname %}
|
||||
* For Mac:
|
||||
* Use: <kbd>Shift</kbd>+<kbd>Command</kbd>+<kbd>P</kbd>
|
||||
* For Windows or Linux:
|
||||
* Use: <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd>
|
||||
1. Type "Diagnostics", and then select **{% data variables.product.prodname_copilot%}: Collect Diagnostics** from the list. This opens a new editor with the relevant information that you can inspect yourself or share with the support team.
|
||||
1. Check the section on **Reachability** to determine if {% data variables.product.prodname_copilot%} can actually access the necessary services.
|
||||
1. Type "Diagnostics", and then select **{% data variables.product.prodname_copilot %}: Collect Diagnostics** from the list. This opens a new editor with the relevant information that you can inspect yourself or share with the support team.
|
||||
1. Check the section on **Reachability** to determine if {% data variables.product.prodname_copilot %} can actually access the necessary services.
|
||||
|
||||
## Viewing Electron logs
|
||||
|
||||
|
|
@ -150,7 +150,7 @@ In rare cases, errors might not be propagated to the corresponding error handler
|
|||
|
||||
{% vimneovim %}
|
||||
|
||||
## Checking if {% data variables.product.prodname_copilot%} is operational
|
||||
## Checking if {% data variables.product.prodname_copilot %} is operational
|
||||
|
||||
To check if GitHub Copilot is operational, run the following command in Vim/Neovim:
|
||||
|
||||
|
|
|
|||
|
|
@ -34,9 +34,9 @@ With {% data variables.product.prodname_copilot_enterprise_short %}, you can als
|
|||
|
||||
## Limitations
|
||||
|
||||
The following {% ifversion fpt%}limitation applies{% else %} limitations apply{% endif %} to {% data variables.product.prodname_copilot_mobile_short %}:
|
||||
The following {% ifversion fpt %}limitation applies{% else %} limitations apply{% endif %} to {% data variables.product.prodname_copilot_mobile_short %}:
|
||||
|
||||
{% ifversion ghec%}
|
||||
{% ifversion ghec %}
|
||||
* Chat responses may be suboptimal if you ask questions about a specific repository that you've selected as a context, and the repository has not been indexed for semantic code search. {% data reusables.copilot.indexing-who-can-do-this %}{% endif %}
|
||||
* The quality of the results from {% data variables.product.prodname_copilot_chat_short %} may, in some situations, be degraded if very large files, or a large number of files, are used as a context for a question.
|
||||
|
||||
|
|
|
|||
|
|
@ -36,7 +36,7 @@ With {% data variables.product.prodname_free_user %}, your personal account incl
|
|||
* {% data variables.product.prodname_dependabot_alerts %}
|
||||
* Deployment protection rules for public repositories
|
||||
* Two-factor authentication enforcement
|
||||
* 500 MB {% data variables.product.prodname_registry %} storage {% ifversion fpt or ghec%}
|
||||
* 500 MB {% data variables.product.prodname_registry %} storage {% ifversion fpt or ghec %}
|
||||
* 120 {% data variables.product.prodname_github_codespaces %} core hours per month
|
||||
* 15 GB {% data variables.product.prodname_github_codespaces %} storage per month {% endif %}
|
||||
* {% data variables.product.prodname_actions %} features:
|
||||
|
|
@ -49,7 +49,7 @@ With {% data variables.product.prodname_free_user %}, your personal account incl
|
|||
In addition to the features available with {% data variables.product.prodname_free_user %} for personal accounts, {% data variables.product.prodname_pro %} includes:
|
||||
* {% data variables.contact.github_support %} via email
|
||||
* 3,000 {% data variables.product.prodname_actions %} minutes per month
|
||||
* 2 GB {% data variables.product.prodname_registry %} storage {% ifversion fpt or ghec%}
|
||||
* 2 GB {% data variables.product.prodname_registry %} storage {% ifversion fpt or ghec %}
|
||||
* 180 {% data variables.product.prodname_github_codespaces %} core hours per month
|
||||
* 20 GB {% data variables.product.prodname_github_codespaces %} storage per month {% endif %}
|
||||
* Advanced tools and insights in private repositories:
|
||||
|
|
|
|||
|
|
@ -69,10 +69,10 @@ To audit access to enterprise-owned resources or user license usage, you can vie
|
|||
|
||||
## Part 3: Managing security with {% data variables.product.prodname_ghe_cloud %}
|
||||
|
||||
* [Managing security with {% data variables.product.prodname_emus %}](#managing-security-with-enterprise-managed-users)
|
||||
* [Managing security without {% data variables.product.prodname_emus %}](#managing-security-without-enterprise-managed-users)
|
||||
* [Managing security with {% data variables.product.prodname_emus %}](#managing-security-with-enterprise-managed-users)
|
||||
* [Managing security without {% data variables.product.prodname_emus %}](#managing-security-without-enterprise-managed-users)
|
||||
|
||||
### Managing security with {% data variables.product.prodname_emus %}
|
||||
### Managing security with {% data variables.product.prodname_emus %}
|
||||
|
||||
With {% data variables.product.prodname_emus %}, access and identity is managed centrally through your identity provider. Two-factor authentication and other access requirements should be enabled and enforced on your IdP.
|
||||
|
||||
|
|
@ -92,7 +92,7 @@ You can configure an allow list for specific IP addresses to restrict access to
|
|||
|
||||
{% data reusables.getting-started.enterprise-advanced-security %}
|
||||
|
||||
### Managing security without {% data variables.product.prodname_emus %}
|
||||
### Managing security without {% data variables.product.prodname_emus %}
|
||||
|
||||
To manage security for your enterprise, you can require two-factor authentication, manage allowed IP addresses, enable SAML single sign-on and team synchronization, and sign up for and enforce GitHub Advanced Security features.
|
||||
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ This tutorial will show you how to upload a group of files to a {% data variable
|
|||
|
||||
Uploading your files to a {% data variables.product.prodname_dotcom %} repository lets you:
|
||||
* **Apply version control** when you make edits to the files, so your project's history is protected and manageable.
|
||||
* **Back up** your work{% ifversion fpt or ghec%}, because your files are now stored in the cloud{% endif %}.
|
||||
* **Back up** your work{% ifversion fpt or ghec %}, because your files are now stored in the cloud{% endif %}.
|
||||
* **Pin** the repository to your personal profile, so that others can see your work.
|
||||
* **Share** and discuss your work with others, either publicly or privately.
|
||||
|
||||
|
|
|
|||
|
|
@ -26,6 +26,6 @@ shortTitle: Feature preview
|
|||
|
||||
You can see a list of features that are available in {% data variables.release-phases.public_preview %} and a brief description for each feature. Each feature includes a link to give feedback.
|
||||
|
||||
{% data reusables.feature-preview.feature-preview-setting %}
|
||||
{% data reusables.feature-preview.feature-preview-setting %}
|
||||
1. To view details for a feature, in the left sidebar, click the feature's name.
|
||||
1. Optionally, to the right of a feature's name, click **Enable** or **Disable**.
|
||||
|
|
|
|||
|
|
@ -215,7 +215,7 @@ For more information, see "[Get an organization migration status](/rest/migratio
|
|||
|
||||
**Note:** If your migration moves to the `failed` state rather than the `exported` state, try starting the migration again. If the migration fails repeatedly, we recommend generating the archives using `ghe-migrator` instead of the API.
|
||||
|
||||
Follow the steps in "[Exporting migration data from your enterprise]({% ifversion not ghes%}/enterprise-server@latest{% endif %}/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise)," adding only one repository to the migration. At the end of the process, you will have a single migration archive with your Git source and metadata, and you can move to step 6 in this article.
|
||||
Follow the steps in "[Exporting migration data from your enterprise]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise)," adding only one repository to the migration. At the end of the process, you will have a single migration archive with your Git source and metadata, and you can move to step 6 in this article.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
|
|
|
|||
|
|
@ -20,4 +20,4 @@ shortTitle: Configure retention period
|
|||
{% data reusables.organizations.navigate-to-org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.organizations.settings-sidebar-actions-general %}
|
||||
{% data reusables.actions.change-retention-period-for-artifacts-logs %}
|
||||
{% data reusables.actions.change-retention-period-for-artifacts-logs %}
|
||||
|
|
|
|||
|
|
@ -220,6 +220,6 @@ You can configure the size limit for {% data variables.product.prodname_actions
|
|||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.settings-sidebar-actions-general %}
|
||||
{% data reusables.actions.change-cache-size-limit %}
|
||||
{% data reusables.actions.change-cache-size-limit %}
|
||||
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@ When you set the base permission for projects in your organization's settings, t
|
|||
|
||||
{% endnote %}
|
||||
|
||||
## Setting a base permission for {% data variables.projects.projects_v2 %} in your organization
|
||||
## Setting a base permission for {% data variables.projects.projects_v2 %} in your organization
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ shortTitle: Custom properties
|
|||
|
||||
Custom properties allow you to decorate your repositories with information such as compliance frameworks, data sensitivity, or project details. Custom properties are private and can only be viewed by people with read permissions to the repository.
|
||||
|
||||
{% ifversion ghec or ghes %}
|
||||
{% ifversion ghec or ghes %}
|
||||
You can use repository properties to determine which repositories to target with a ruleset. For more information, see "[AUTOTITLE](/organizations/managing-organization-settings/creating-rulesets-for-repositories-in-your-organization#targeting-repositories-by-properties-in-your-organization)."
|
||||
{% endif %}
|
||||
|
||||
|
|
@ -64,7 +64,7 @@ People with read permissions to a repository can view the values of custom prope
|
|||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
1. In the "Code and automation" section of the sidebar, click **{% octicon "tools" aria-hidden="true"%} Custom properties**.
|
||||
1. In the "Code and automation" section of the sidebar, click **{% octicon "tools" aria-hidden="true" %} Custom properties**.
|
||||
|
||||
## Searching and filtering repositories by custom properties values
|
||||
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ versions:
|
|||
|
||||
## {% data variables.product.prodname_github_apps %}
|
||||
|
||||
Organization owners can install {% data variables.product.prodname_github_apps %} on their organization. Repository admins can also install a {% data variables.product.prodname_github_app %} on the organization if the app does not request organization resources and if they only grant the app access to repositories where they are an admin. Organization members can submit a request for their organization owner to install a {% data variables.product.prodname_github_app %} on the organization. For more information, see {% ifversion fpt or ghec%}"[AUTOTITLE](/apps/using-github-apps/installing-an-app-in-your-organization)."{% else %}"[AUTOTITLE](/apps/maintaining-github-apps/installing-github-apps)."{% endif %}
|
||||
Organization owners can install {% data variables.product.prodname_github_apps %} on their organization. Repository admins can also install a {% data variables.product.prodname_github_app %} on the organization if the app does not request organization resources and if they only grant the app access to repositories where they are an admin. Organization members can submit a request for their organization owner to install a {% data variables.product.prodname_github_app %} on the organization. For more information, see {% ifversion fpt or ghec %}"[AUTOTITLE](/apps/using-github-apps/installing-an-app-in-your-organization)."{% else %}"[AUTOTITLE](/apps/maintaining-github-apps/installing-github-apps)."{% endif %}
|
||||
|
||||
{% ifversion limit-app-access-requests %}Organization owners can prevent outside collaborators from requesting {% data variables.product.prodname_github_apps %} or from installing a {% data variables.product.prodname_github_app %} even if the collaborator is a repository admin. For more information, see "[AUTOTITLE](/organizations/managing-programmatic-access-to-your-organization/limiting-oauth-app-and-github-app-access-requests)."{% endif %}
|
||||
|
||||
|
|
|
|||
|
|
@ -42,7 +42,7 @@ This registry supports granular permissions. {% data reusables.package_registry.
|
|||
Use the following command to authenticate to {% data variables.product.prodname_registry %} in a {% data variables.product.prodname_actions %} workflow using the `GITHUB_TOKEN` instead of hardcoding a {% data variables.product.pat_generic %} in a nuget.config file in the repository:
|
||||
|
||||
```shell
|
||||
dotnet nuget add source --username USERNAME --password {%raw%}${{ secrets.GITHUB_TOKEN }}{% endraw %} --store-password-in-clear-text --name github "https://{% ifversion fpt or ghec %}nuget.pkg.github.com{% else %}nuget.HOSTNAME{% endif %}/NAMESPACE/index.json"
|
||||
dotnet nuget add source --username USERNAME --password {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %} --store-password-in-clear-text --name github "https://{% ifversion fpt or ghec %}nuget.pkg.github.com{% else %}nuget.HOSTNAME{% endif %}/NAMESPACE/index.json"
|
||||
```
|
||||
|
||||
Replace `NAMESPACE` with the name of the personal account or organization {% ifversion packages-nuget-v2 %}to which your packages are scoped{% else %}that owns the repository where your packages are hosted{% endif %}.
|
||||
|
|
@ -118,7 +118,7 @@ You can publish a package to {% data variables.product.prodname_registry %} by a
|
|||
Replace `OWNER` with your username or company name, and `YOUR_GITHUB_PAT` with your {% data variables.product.pat_generic %}.
|
||||
|
||||
```shell
|
||||
dotnet nuget add source --username OWNER --password {%raw%}YOUR_GITHUB_PAT{% endraw %} --store-password-in-clear-text --name github "https://{% ifversion fpt or ghec %}nuget.pkg.github.com{% else %}nuget.HOSTNAME{% endif %}/OWNER/index.json"
|
||||
dotnet nuget add source --username OWNER --password {% raw %}YOUR_GITHUB_PAT{% endraw %} --store-password-in-clear-text --name github "https://{% ifversion fpt or ghec %}nuget.pkg.github.com{% else %}nuget.HOSTNAME{% endif %}/OWNER/index.json"
|
||||
```
|
||||
|
||||
{% ifversion packages-nuget-v2 %}
|
||||
|
|
|
|||
|
|
@ -176,7 +176,7 @@ You can require that changes are successfully deployed to specific environments
|
|||
Locking a branch will make the branch read-only and ensures that no commits can be made to the branch. Locked branches can also not be deleted.
|
||||
|
||||
By default, a forked repository does not support syncing from its upstream repository. You can enable **Allow fork syncing** to pull changes from the upstream repository while preventing other contributions to the fork's branch.
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
||||
### Do not allow bypassing the above settings
|
||||
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ You can use the REST and GraphQL APIs to manage rulesets. For more information,
|
|||
|
||||
## Viewing rulesets for a repository
|
||||
|
||||
On the "Rulesets" page, anyone with read access to the repository can view the active rulesets targeting a certain {% ifversion push-rulesets%}branch, tag, or push restriction.{% else %}branch or tag.{% endif %} {% ifversion repo-rules-enterprise %}You will also see rulesets running in "Evaluate" mode, which are not enforced.{% endif %}
|
||||
On the "Rulesets" page, anyone with read access to the repository can view the active rulesets targeting a certain {% ifversion push-rulesets %}branch, tag, or push restriction.{% else %}branch or tag.{% endif %} {% ifversion repo-rules-enterprise %}You will also see rulesets running in "Evaluate" mode, which are not enforced.{% endif %}
|
||||
|
||||
{% ifversion push-rulesets %}
|
||||
|
||||
|
|
|
|||
|
|
@ -68,7 +68,7 @@ A CODEOWNERS file uses a pattern that follows most of the same rules used in [gi
|
|||
|
||||
If you want to match two or more code owners with the same pattern, all the code owners must be on the same line. If the code owners are not on the same line, the pattern matches only the last mentioned code owner.
|
||||
|
||||
{% ifversion fpt or ghec%}In most cases, you{% else %}You{% endif %} can also refer to a user by an email address that has been added to their account, for example `user@example.com`. {% ifversion fpt or ghec %} You cannot use an email address to refer to a {% data variables.enterprise.prodname_managed_user %}. For more information about {% data variables.enterprise.prodname_managed_users %}, see "[AUTOTITLE](/enterprise-cloud@latest/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %}
|
||||
{% ifversion fpt or ghec %}In most cases, you{% else %}You{% endif %} can also refer to a user by an email address that has been added to their account, for example `user@example.com`. {% ifversion fpt or ghec %} You cannot use an email address to refer to a {% data variables.enterprise.prodname_managed_user %}. For more information about {% data variables.enterprise.prodname_managed_users %}, see "[AUTOTITLE](/enterprise-cloud@latest/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %}
|
||||
|
||||
CODEOWNERS paths are case sensitive, because {% data variables.product.prodname_dotcom %} uses a case sensitive file system. Since CODEOWNERS are evaluated by {% data variables.product.prodname_dotcom %}, even systems that are case insensitive (for example, macOS) must use paths and files that are cased correctly in the CODEOWNERS file.
|
||||
|
||||
|
|
|
|||
|
|
@ -124,7 +124,7 @@ By default, when you create a new repository in your personal account, workflows
|
|||
|
||||
{% ifversion internal-actions %}Actions and reusable workflows in your internal repositories can be shared with internal and private repositories in the same organization or enterprise.{% else %}Members of your enterprise can use internal repositories to work on projects without sharing information publicly.{% endif %} For information about internal repositories, see "[AUTOTITLE](/repositories/creating-and-managing-repositories/about-repositories#about-internal-repositories)."
|
||||
|
||||
You can use the steps below to configure whether {% ifversion internal-actions%}actions and {% endif %}reusable workflows in an internal repository can be accessed from outside the repository.{% ifversion internal-actions %} For more information, see "[AUTOTITLE](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)." Alternatively, you can use the REST API to set, or get details of the level of access. For more information, see "[AUTOTITLE](/rest/actions/permissions#get-the-level-of-access-for-workflows-outside-of-the-repository)" and "[AUTOTITLE](/rest/actions/permissions#set-the-level-of-access-for-workflows-outside-of-the-repository)."{% endif %}
|
||||
You can use the steps below to configure whether {% ifversion internal-actions %}actions and {% endif %}reusable workflows in an internal repository can be accessed from outside the repository.{% ifversion internal-actions %} For more information, see "[AUTOTITLE](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)." Alternatively, you can use the REST API to set, or get details of the level of access. For more information, see "[AUTOTITLE](/rest/actions/permissions#get-the-level-of-access-for-workflows-outside-of-the-repository)" and "[AUTOTITLE](/rest/actions/permissions#set-the-level-of-access-for-workflows-outside-of-the-repository)."{% endif %}
|
||||
|
||||
1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of the internal repository.
|
||||
1. Under your repository name, click {% octicon "gear" aria-hidden="true" %} **Settings**.
|
||||
|
|
@ -201,7 +201,7 @@ You can also define a custom retention period for a specific artifact created by
|
|||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% data reusables.repositories.settings-sidebar-actions-general %}
|
||||
{% data reusables.actions.change-retention-period-for-artifacts-logs %}
|
||||
{% data reusables.actions.change-retention-period-for-artifacts-logs %}
|
||||
|
||||
{% ifversion actions-cache-policy-apis %}
|
||||
|
||||
|
|
|
|||
|
|
@ -62,7 +62,7 @@ If you get a `404 Not Found` response when you know that the resource that you a
|
|||
* If you are using an {% data variables.product.prodname_oauth_app %} user access token, you should ensure that:
|
||||
* The token has the scopes that are required to use the endpoint. For more information, see "[AUTOTITLE](/apps/oauth-apps/building-oauth-apps/scopes-for-oauth-apps#available-scopes)."
|
||||
* The user that authorized the token has any permissions that are required to use the endpoint. For example, if an endpoint can only be used by organization owners, only users that are owners of the affected organization can use the endpoint.
|
||||
* The organization has not blocked OAuth app access, if you are using an endpoint that will affect resources owned by an organization. App owners cannot see whether their app is blocked, but they can instruct users of the app to check this. For more information, see {% ifversion fpt or ghec%}"[AUTOTITLE](/organizations/managing-oauth-access-to-your-organizations-data/about-oauth-app-access-restrictions)."{% else %}"[AUTOTITLE](/free-pro-team@latest/organizations/managing-oauth-access-to-your-organizations-data/about-oauth-app-access-restrictions)" in the {% data variables.product.prodname_free_team %} documentation.{% endif %}
|
||||
* The organization has not blocked OAuth app access, if you are using an endpoint that will affect resources owned by an organization. App owners cannot see whether their app is blocked, but they can instruct users of the app to check this. For more information, see {% ifversion fpt or ghec %}"[AUTOTITLE](/organizations/managing-oauth-access-to-your-organizations-data/about-oauth-app-access-restrictions)."{% else %}"[AUTOTITLE](/free-pro-team@latest/organizations/managing-oauth-access-to-your-organizations-data/about-oauth-app-access-restrictions)" in the {% data variables.product.prodname_free_team %} documentation.{% endif %}
|
||||
* The token has not been expired or revoked. For more information, see "[AUTOTITLE](/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation)."
|
||||
* If you are using `GITHUB_TOKEN` in a {% data variables.product.prodname_actions %} workflow, you should ensure that:
|
||||
* The endpoint is only affecting resources owned by the repository where the workflow is running. If you need to access resources outside of that repository, such as resources owned by an organization or resources owned by another repository, you should use a {% data variables.product.pat_generic %} or an access token for a {% data variables.product.prodname_github_app %}.
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@ Supported languages for code navigation include:
|
|||
|
||||
## Limitations
|
||||
|
||||
We have indexed many public repositories for code search, and continue to index more. Additionally, the private repositories of {% data variables.product.prodname_dotcom%} users are indexed and searchable by those that already have access to those private repositories on {% data variables.product.prodname_dotcom %}. However, very large repositories may not be indexed at this time, and not all code is indexed.
|
||||
We have indexed many public repositories for code search, and continue to index more. Additionally, the private repositories of {% data variables.product.prodname_dotcom %} users are indexed and searchable by those that already have access to those private repositories on {% data variables.product.prodname_dotcom %}. However, very large repositories may not be indexed at this time, and not all code is indexed.
|
||||
|
||||
The current limitations on indexed code are:
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ topics:
|
|||
- GitHub search
|
||||
---
|
||||
|
||||
## About using {% data variables.product.prodname_dotcom%} code search
|
||||
## About using {% data variables.product.prodname_dotcom %} code search
|
||||
|
||||
{% data variables.product.prodname_dotcom %} indexes repositories you own and repositories in organizations you are a member of, whether public, private, or internal. This means that you can search across all of your repositories, in addition to the public repositories on {% data variables.product.prodname_dotcom %} that have already been indexed. Only users with permission to view your code will be able to see your code in search results. Forks are indexed and searchable in the same way as other repositories.
|
||||
|
||||
|
|
|
|||
|
|
@ -72,7 +72,7 @@ You can filter issues and pull requests based on whether they're open or closed
|
|||
| `is:open` | [**performance is:open is:issue**](https://github.com/search?q=performance+is%3Aopen+is%3Aissue&type=Issues) matches open issues with the word "performance."
|
||||
| `is:closed` | [**android is:closed**](https://github.com/search?utf8=%E2%9C%93&q=android+is%3Aclosed&type=) matches closed issues and pull requests with the word "android."
|
||||
|
||||
{% ifversion merge-queue %}
|
||||
{% ifversion merge-queue %}
|
||||
|
||||
## Search for pull requests in the merge queue
|
||||
|
||||
|
|
|
|||
|
|
@ -48,7 +48,7 @@ After you create your ticket, you can view your ticket and the responses from {%
|
|||
## Prerequisites
|
||||
|
||||
{% ifversion ghec %}If you use an enterprise account, there{% else %}There{% endif %} are some steps you should follow before you start using the {% data variables.contact.enterprise_portal %}. For more information, see "[Getting started with the {% data variables.contact.enterprise_portal %}](/support/contacting-github-support/getting-started-with-the-github-support-portal)."
|
||||
{% endif%}
|
||||
{% endif %}
|
||||
|
||||
## What to include in your support ticket
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
After configuring your Azure resources, you can use an Azure Virtual Network (VNET) for private networking by creating a network configuration{% ifversion ghec%} at the enterprise or organization level{% else %} at the organization level{% endif %}. Then, you can associate that network configuration to runner groups. For more information about runner groups, see "[AUTOTITLE](/actions/using-github-hosted-runners/about-larger-runners/controlling-access-to-larger-runners)."
|
||||
After configuring your Azure resources, you can use an Azure Virtual Network (VNET) for private networking by creating a network configuration{% ifversion ghec %} at the enterprise or organization level{% else %} at the organization level{% endif %}. Then, you can associate that network configuration to runner groups. For more information about runner groups, see "[AUTOTITLE](/actions/using-github-hosted-runners/about-larger-runners/controlling-access-to-larger-runners)."
|
||||
|
||||
Once the network configuration is associated with a runner group, all runners in that group will have access to the Azure VNET that has been connected to the underlying configuration.
|
||||
|
||||
|
|
|
|||
|
|
@ -30,4 +30,4 @@ jobs:
|
|||
|
||||
{% endraw %}
|
||||
|
||||
{%endif%}
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -2,10 +2,10 @@
|
|||
1. Optionally, to select a time period to view usage metrics for, choose an option from the **Period** drop down menu at the top right of the page. For more information, see "[Understanding {% data variables.product.prodname_actions %} metrics aggregation](#understanding-github-actions-metrics-aggregation)."
|
||||
1. Click on the tab that contains the metrics you would like to view. For more information, see "[About {% data variables.product.prodname_actions %} usage metrics](#about-github-actions-usage-metrics) or "[About {% data variables.product.prodname_actions %} performance metrics](#about-github-actions-performance-metrics)."
|
||||
1. Optionally, to filter the data displayed in a tab, create a filter.
|
||||
1. Click on the **{% octicon "filter" aria-hidden="true" %} Filter** button.
|
||||
1. Click **{% octicon "plus" aria-hidden="true" %} Add a filter**.
|
||||
1. Click on the **{% octicon "filter" aria-hidden="true" %} Filter** button.
|
||||
1. Click **{% octicon "plus" aria-hidden="true" %} Add a filter**.
|
||||
1. Choose a metric you would like to filter results by.
|
||||
1. Depending on the metric you chose, fill out information in the "Qualifier," "Operator," and "Value" columns.
|
||||
1. Optionally, click **{% octicon "plus" aria-hidden="true" %} Add a filter** to add another filter.
|
||||
1. Optionally, click **{% octicon "plus" aria-hidden="true" %} Add a filter** to add another filter.
|
||||
1. Click **Apply**.
|
||||
1. Optionally, to download usage metrics to a CSV file, click {% octicon "download" aria-label="Download report" %}.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
{% ifversion fpt or ghec %}If you are accessing an organization that uses SAML SSO{% ifversion pat-v2%} and you are using a {% data variables.product.pat_v1 %}{% endif %}, you must also authorize your {% data variables.product.pat_generic %} to access the organization before you authenticate. For more information, see "[AUTOTITLE](/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)" and "[AUTOTITLE](/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)."{% endif %}
|
||||
{% ifversion fpt or ghec %}If you are accessing an organization that uses SAML SSO{% ifversion pat-v2 %} and you are using a {% data variables.product.pat_v1 %}{% endif %}, you must also authorize your {% data variables.product.pat_generic %} to access the organization before you authenticate. For more information, see "[AUTOTITLE](/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)" and "[AUTOTITLE](/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)."{% endif %}
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@ npm | `npm` | v6, v7, v8, v9 | {% octicon "check" aria-l
|
|||
pipenv | `pip` | <= 2021-05-29 | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "x" aria-label="Not supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "x" aria-label="Not supported" %} |
|
||||
| {% ifversion dependabot-PEP621-support %}[pip-compile](#pip-and-pip-compile){% else %}pip-compile{% endif %} | `pip` | 6.1.0 | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "x" aria-label="Not supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "x" aria-label="Not supported" %} |
|
||||
| {% ifversion dependabot-updates-pnpm-support %} |
|
||||
| {% ifversion dependabot-updates-pnpmv9-support %}pnpm{%else %}[pnpm](#pnpm){% endif %} | `npm` | v7, v8, v9 | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} {% ifversion dependabot-updates-pnpmv9-support %}{% else %}(v7 and v8 only){% endif %}| {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "x" aria-label="Not supported" %} |
|
||||
| {% ifversion dependabot-updates-pnpmv9-support %}pnpm{% else %}[pnpm](#pnpm){% endif %} | `npm` | v7, v8, v9 | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} {% ifversion dependabot-updates-pnpmv9-support %}{% else %}(v7 and v8 only){% endif %}| {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "x" aria-label="Not supported" %} |
|
||||
| {% endif %} |
|
||||
poetry | `pip` | v1 | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "x" aria-label="Not supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "x" aria-label="Not supported" %} |
|
||||
[pub](#pub) | `pub` | v2 | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% ifversion dependabot-updates-pub-private-registry %}{% octicon "check" aria-label="Supported" %}{% else %}{% octicon "x" aria-label="Not supported" %}{% endif %} | {% ifversion dependabot-updates-pub-private-registry %}{% octicon "check" aria-label="Supported" %}{% else %}{% octicon "x" aria-label="Not supported" %}{% endif %} | {% octicon "x" aria-label="Not supported" %} |
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
{% ifversion not ghec%}By default, a{% else %}A{% endif %} user account is considered to be dormant if it has not been active for 90 days. {% ifversion not ghec %}You can configure the length of time a user must be inactive to be considered dormant{% ifversion ghes%} and choose to suspend dormant users to release user licenses{% endif %}.{% endif %}
|
||||
{% ifversion not ghec %}By default, a{% else %}A{% endif %} user account is considered to be dormant if it has not been active for 90 days. {% ifversion not ghec %}You can configure the length of time a user must be inactive to be considered dormant{% ifversion ghes %} and choose to suspend dormant users to release user licenses{% endif %}.{% endif %}
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
A user is considered active if the user has performed any of the following activities on {% ifversion fpt or ghes %}{% data variables.location.product_location %}{% elsif ghec %}your enterprise{% endif %}.
|
||||
|
||||
* {% ifversion ghec%}Authenticating to access your enterprise's resources via SAML SSO{% else %}Signing into {% data variables.location.product_location %} {% endif %}
|
||||
* {% ifversion ghec %}Authenticating to access your enterprise's resources via SAML SSO{% else %}Signing into {% data variables.location.product_location %} {% endif %}
|
||||
* Creating a repository
|
||||
* Pushing to a repository via HTTPS{% ifversion ghes %}
|
||||
* Pushing to a repository via SSH{% endif %}
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
{% ifversion ghec%}
|
||||
{% ifversion ghec %}
|
||||
{% note %}
|
||||
|
||||
**Note**: If your enterprise uses {% data variables.product.prodname_emus %}, you must follow a different process to configure SAML single sign-on. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users)."
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
{% ifversion ghec%}
|
||||
{% ifversion ghec %}
|
||||
{% note %}
|
||||
|
||||
**Note**: If your enterprise uses {% data variables.product.prodname_emus %}, you do not need to use team synchronization. Instead, you can manage team membership via the SCIM configuration you created while setting up your enterprise. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups)."
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
1. Under **{% octicon "gear" aria-label="The Settings gear" %} Settings**, click **{%ifversion ghes %}Messages{% elsif ghec %}Announcement{% endif %}**.
|
||||
1. Under **{% octicon "gear" aria-label="The Settings gear" %} Settings**, click **{% ifversion ghes %}Messages{% elsif ghec %}Announcement{% endif %}**.
|
||||
|
|
|
|||
|
|
@ -5,4 +5,4 @@ While setting up your trial of {% data variables.product.prodname_ghe_cloud %},
|
|||
* Enterprise with personal accounts
|
||||
* Enterprise with managed users
|
||||
|
||||
To help you decide which choice is best for your enterprise, see "[AUTOTITLE]({% ifversion not ghec%}/enterprise-cloud@latest{% endif %}/admin/identity-and-access-management/understanding-iam-for-enterprises/choosing-an-enterprise-type-for-github-enterprise-cloud){% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
|
||||
To help you decide which choice is best for your enterprise, see "[AUTOTITLE]({% ifversion not ghec %}/enterprise-cloud@latest{% endif %}/admin/identity-and-access-management/understanding-iam-for-enterprises/choosing-an-enterprise-type-for-github-enterprise-cloud){% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
{% ifversion code-view-ui %}
|
||||
{% ifversion code-view-ui %}
|
||||
1. Above the new content, click **Preview**.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
Organizations{% ifversion ghec%} and enterprises{% endif %} with a subscription to {% data variables.product.prodname_copilot_for_business %} or {% data variables.product.prodname_copilot_enterprise %}.
|
||||
Organizations{% ifversion ghec %} and enterprises{% endif %} with a subscription to {% data variables.product.prodname_copilot_for_business %} or {% data variables.product.prodname_copilot_enterprise %}.
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
{%- ifversion fpt or ghec %}
|
||||
{% data variables.product.prodname_dependabot_alerts %} are free to use for all repositories on {% data variables.product.prodname_dotcom %}. {% ifversion fpt%}Advanced capabilities, like the ability to create {% data variables.dependabot.custom_rules %} for {% data variables.product.prodname_dependabot_alerts %}, are available (for free) on public repositories only.{% elsif ghec %} Advanced capabilities, like reachability analysis and the ability to create {% data variables.dependabot.custom_rules %}, are available on any organization-owned repositories, when you have a license for {% data variables.product.prodname_GH_advanced_security %}.{% endif %}
|
||||
{% data variables.product.prodname_dependabot_alerts %} are free to use for all repositories on {% data variables.product.prodname_dotcom %}. {% ifversion fpt %}Advanced capabilities, like the ability to create {% data variables.dependabot.custom_rules %} for {% data variables.product.prodname_dependabot_alerts %}, are available (for free) on public repositories only.{% elsif ghec %} Advanced capabilities, like reachability analysis and the ability to create {% data variables.dependabot.custom_rules %}, are available on any organization-owned repositories, when you have a license for {% data variables.product.prodname_GH_advanced_security %}.{% endif %}
|
||||
|
||||
{%- elsif ghes %}
|
||||
{% data variables.product.prodname_dependabot_alerts %} are free to use for repositories (user-owned and organization-owned) on {% data variables.product.prodname_ghe_server %}, provided enterprise administrators enable the feature for your enterprise.{% ifversion dependabot-auto-triage-rules %} Advanced capabilities, like the ability to create {% data variables.dependabot.custom_rules %}, are available to all organization-owned repositories, when you have a license for {% data variables.product.prodname_GH_advanced_security %}.{% endif %}
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
1. In the sidebar, select **{% octicon "report" aria-hidden="true"%} Moderation**, then click **Blocked users**.
|
||||
1. In the sidebar, select **{% octicon "report" aria-hidden="true" %} Moderation**, then click **Blocked users**.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
{% ifversion fpt or ghec %}
|
||||
{% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud%}{% else %}You{% endif %} can use team synchronization to automatically add and remove organization members to teams through an identity provider. For more information, see "[Synchronizing a team with an identity provider group]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
|
||||
{% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% else %}You{% endif %} can use team synchronization to automatically add and remove organization members to teams through an identity provider. For more information, see "[Synchronizing a team with an identity provider group]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
{%- ifversion ghec %}
|
||||
1. Optionally, if you're publishing a project site from a private or internal repository, choose the visibility for your site. Under "{% data variables.product.prodname_pages %}", select the visibility dropdown menu, then select public or private.
|
||||
|
||||
{% indented_data_reference reusables.pages.privately-publish-ghec-only spaces=3%}
|
||||
{% indented_data_reference reusables.pages.privately-publish-ghec-only spaces=3 %}
|
||||
{%- endif %}
|
||||
|
|
|
|||
|
|
@ -3,4 +3,4 @@
|
|||
|
||||
{% else %}
|
||||
|
||||
{% endif%}
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
1. In the "Code and automation" section of the sidebar, click **{% octicon "tag" aria-hidden="true"%} Tags**.
|
||||
1. In the "Code and automation" section of the sidebar, click **{% octicon "tag" aria-hidden="true" %} Tags**.
|
||||
|
|
|
|||
|
|
@ -7,5 +7,5 @@
|
|||
{% endif %}
|
||||
|
||||
{% ifversion security-overview-3-tab-dashboard %}{% else %}
|
||||
1. For the alert trends graph at the top of the page, you can click **{% octicon "shield" aria-hidden="true" %} Open alerts** or **{% octicon "shield-x" aria-hidden="true" %} Closed alerts** to toggle between showing the trends for open or closed alerts. The toggle will only affect the alert trends graph. For more information, see "[Alert trends graph](#alert-trends-graph)."
|
||||
1. For the alert trends graph at the top of the page, you can click **{% octicon "shield" aria-hidden="true" %} Open alerts** or **{% octicon "shield-x" aria-hidden="true" %} Closed alerts** to toggle between showing the trends for open or closed alerts. The toggle will only affect the alert trends graph. For more information, see "[Alert trends graph](#alert-trends-graph)."
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
1. In the sidebar, click **{% octicon "meter" aria-hidden="true" %} Coverage** to display the "Security coverage" view.
|
||||
1. In the sidebar, click **{% octicon "meter" aria-hidden="true" %} Coverage** to display the "Security coverage" view.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
1. In the "Security" section of the sidebar, click **{% octicon "shield-lock" aria-hidden="true"%} Code security and analysis**.
|
||||
1. In the "Security" section of the sidebar, click **{% octicon "shield-lock" aria-hidden="true" %} Code security and analysis**.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
If a request URL does not include a `{username}` parameter then the response will be for the signed-in user (and you must pass [authentication information](/rest/overview/authenticating-to-the-rest-api) with your request). Additional private information, such as whether a user has two-factor authentication enabled, is included when authenticated through{% ifversion ghes%} Basic Authentication or{% endif %} OAuth with the `user` scope.
|
||||
If a request URL does not include a `{username}` parameter then the response will be for the signed-in user (and you must pass [authentication information](/rest/overview/authenticating-to-the-rest-api) with your request). Additional private information, such as whether a user has two-factor authentication enabled, is included when authenticated through{% ifversion ghes %} Basic Authentication or{% endif %} OAuth with the `user` scope.
|
||||
|
|
|
|||
Загрузка…
Ссылка в новой задаче