зеркало из https://github.com/github/docs.git
Hide decorative octicons (#36816)
Co-authored-by: Isaac Brown <101839405+isaacmbrown@users.noreply.github.com>
This commit is contained in:
Laura Coursen
GitHub
Родитель
7ded1af3b4
Коммит
0371abe115
|
|
@ -16,5 +16,5 @@ redirect_from:
|
|||
If you feel that tabbed indentation in code rendered on {% data variables.product.product_name %} takes up too much, or too little space, you can change this in your settings.
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
1. In the left sidebar, click **{% octicon "paintbrush" aria-label="The paintbrush icon" %} Appearance**.
|
||||
1. In the left sidebar, click **{% octicon "paintbrush" aria-hidden="true" %} Appearance**.
|
||||
2. Scroll down to "Tab size preference" and use the dropdown menu to choose your preference.
|
||||
|
|
@ -22,7 +22,7 @@ You can access {% data variables.product.company_short %}'s compliance reports i
|
|||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.enterprise-accounts-compliance-tab %}
|
||||
1. Under "Resources", to the right of the report you want to access, click {% octicon "download" aria-label="The Download icon" %} **Download** or {% octicon "link-external" aria-label="The external link icon" %} **View**.
|
||||
1. Under "Resources", to the right of the report you want to access, click {% octicon "download" aria-hidden="true" %} **Download** or {% octicon "link-external" aria-hidden="true" %} **View**.
|
||||
|
||||
{% data reusables.security.compliance-report-screenshot %}
|
||||
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ Enterprise owners can prevent {% data variables.product.pat_v2 %}s from accessin
|
|||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.policies-tab %}
|
||||
1. Under {% octicon "law" aria-label="The law icon" %} **Policies**, click **Organizations**.
|
||||
1. Under {% octicon "law" aria-hidden="true" %} **Policies**, click **Organizations**.
|
||||
1. Under **Restrict access via {% data variables.product.pat_v2 %}s**, select the option that meets your needs:
|
||||
- **Allow organizations to configure access requirements**: Each organization owned by the enterprise can decide whether to restrict access by {% data variables.product.pat_v2 %}s.
|
||||
- **Restrict access via {% data variables.product.pat_v2 %}s**: {% data variables.product.pat_v2_caps %}s cannot access organizations owned by the enterprise. SSH keys created by {% data variables.product.pat_v2 %}s will continue to work. Organizations cannot override this setting.
|
||||
|
|
@ -41,7 +41,7 @@ Enterprise owners can require that all organizations owned by the enterprise mus
|
|||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.policies-tab %}
|
||||
1. Under {% octicon "law" aria-label="The law icon" %} **Policies**, click **Organizations**.
|
||||
1. Under {% octicon "law" aria-hidden="true" %} **Policies**, click **Organizations**.
|
||||
1. Under **Require approval of {% data variables.product.pat_v2 %}s**, select the option that meets your needs:
|
||||
- **Allow organizations to configure approval requirements**: Each organization owned by the enterprise can decide whether to require approval of {% data variables.product.pat_v2 %} that can access the organization.
|
||||
- **Require organizations to use the approval flow**: All organizations owned by the enterprise must approve each {% data variables.product.pat_v2 %} that can access the organization. {% data variables.product.pat_v2_caps %}s created by organization owners will not need approval. Organizations cannot override this setting.
|
||||
|
|
@ -54,7 +54,7 @@ Enterprise owners can prevent {% data variables.product.pat_v1_plural %} from ac
|
|||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.policies-tab %}
|
||||
1. Under {% octicon "law" aria-label="The law icon" %} **Policies**, click **Organizations**.
|
||||
1. Under {% octicon "law" aria-hidden="true" %} **Policies**, click **Organizations**.
|
||||
1. Under **Restrict {% data variables.product.pat_v1_plural %} from accessing your organizations**, select the option that meets your needs:
|
||||
- **Allow organizations to configure {% data variables.product.pat_v1_plural %} access requirements**: Each organization owned by the enterprise can decide whether to restrict access by {% data variables.product.pat_v1_plural %}.
|
||||
- **Restrict access via {% data variables.product.pat_v1_plural %}**: {% data variables.product.pat_v1_caps_plural %} cannot access the enterprise or organizations owned by the enterprise. SSH keys created by {% data variables.product.pat_v1_plural %} will continue to work. Organizations cannot override this setting.
|
||||
|
|
|
|||
|
|
@ -29,7 +29,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-label="The repo icon" %} **Repositories** section, click the {% octicon "trash" aria-label="The trash icon" %} **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**.
|
||||
|
||||
|
|
|
|||
|
|
@ -36,7 +36,7 @@ You can download a CSV file containing the membership information report for you
|
|||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.people-tab %}
|
||||
1. To the right of "Members", click **{% octicon "download" aria-label="The download icon" %} CSV Report**.
|
||||
1. To the right of "Members", click **{% octicon "download" aria-hidden="true" %} CSV Report**.
|
||||
|
||||
- If your enterprise has less than 1,000 members, the report will download immediately.
|
||||
- If your enterprise has 1,000 or more members, you'll soon receive an email with a link to download the report.
|
||||
|
|
|
|||
|
|
@ -140,7 +140,7 @@ If your enterprise uses {% data variables.product.prodname_emus %}, you can view
|
|||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.people-tab %}
|
||||
1. Under "People", click **Suspended**.
|
||||
1. Under "People", click **Suspended**.
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
|
@ -172,7 +172,7 @@ You can view a list of members in your enterprise who don't have an email addres
|
|||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.verified-domains-tab %}
|
||||
1. Under "Notification preferences", click the {% octicon "eye" aria-label="The github eye icon" %} **View enterprise members without an approved or verified domain email** link.
|
||||
1. Under "Notification preferences", click the {% octicon "eye" aria-hidden="true" %} **View enterprise members without an approved or verified domain email** link.
|
||||
{% endif %}
|
||||
|
||||
## Further reading
|
||||
|
|
|
|||
|
|
@ -90,7 +90,7 @@ When using a {% data variables.product.pat_generic %} in a script, you can store
|
|||
{% ifversion fpt or ghec %}1. [Verify your email address](/get-started/signing-up-for-github/verifying-your-email-address), if it hasn't been verified yet.{% endif %}
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.developer_settings %}
|
||||
1. In the left sidebar, under **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}s**, click **Fine-grained tokens**.
|
||||
1. In the left sidebar, under **{% octicon "key" aria-hidden="true" %} {% data variables.product.pat_generic_caps %}s**, click **Fine-grained tokens**.
|
||||
1. Click **Generate new token**.
|
||||
1. Under **Token name**, enter a name for the token.
|
||||
1. Under **Expiration**, select an expiration for the token.
|
||||
|
|
@ -131,7 +131,7 @@ If you selected an organization as the resource owner and the organization requi
|
|||
{% ifversion fpt or ghec %}1. [Verify your email address](/get-started/signing-up-for-github/verifying-your-email-address), if it hasn't been verified yet.{% endif %}
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.developer_settings %}
|
||||
{% ifversion pat-v2 %}1. In the left sidebar, under **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}s**, click **Tokens (classic)**.{% else %}{% data reusables.user-settings.personal_access_tokens %}{% endif %}
|
||||
{% ifversion pat-v2 %}1. In the left sidebar, under **{% octicon "key" aria-hidden="true" %} {% data variables.product.pat_generic_caps %}s**, click **Tokens (classic)**.{% else %}{% data reusables.user-settings.personal_access_tokens %}{% endif %}
|
||||
{% ifversion pat-v2%}1. Select **Generate new token**, then click **Generate new token (classic)**.{% else %}{% data reusables.user-settings.generate_new_token %}{% endif %}
|
||||
5. In the "Note" field, give your token a descriptive name.
|
||||
6. To give your token an expiration, select **Expiration**, then choose a default option or click **Custom** to enter a date.
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ shortTitle: Deploy keys
|
|||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
|
||||
3. In the "Security" section of the sidebar, click **{% octicon "key" aria-label="The key icon" %} Deploy keys**.
|
||||
3. In the "Security" section of the sidebar, click **{% octicon "key" aria-hidden="true" %} Deploy keys**.
|
||||
{% else %}
|
||||
3. In the left sidebar, click **Deploy keys**.
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ The security log lists all actions performed within the last 90 days.
|
|||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
|
||||
1. In the "Archives" section of the sidebar, click **{% octicon "log" aria-label="The log icon" %} Security log**.
|
||||
1. In the "Archives" section of the sidebar, click **{% octicon "log" aria-hidden="true" %} Security log**.
|
||||
{% else %}
|
||||
1. In the user settings sidebar, click **Security log**.
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -87,7 +87,7 @@ You can download the {% data variables.product.prodname_advanced_security %} lic
|
|||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
1. In the "Security" section of the sidebar, click {% octicon "codescan" aria-label="The {% data variables.product.prodname_code_scanning %} icon" %} **Code security and analysis**.
|
||||
1. In the "Security" section of the sidebar, click {% octicon "codescan" aria-hidden="true" %} **Code security and analysis**.
|
||||
1. In the "{% data variables.product.prodname_GH_advanced_security %} repositories" section, next to the repository you want usage information for, select {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Download CSV report**.
|
||||
|
||||
|
||||
|
|
@ -99,7 +99,7 @@ You can download the {% data variables.product.prodname_advanced_security %} lic
|
|||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
1. Underneath "{% data variables.product.prodname_GH_advanced_security %}," next to "Committers", click **{% octicon "download" aria-label="The download icon" %} CSV report**.
|
||||
1. Underneath "{% data variables.product.prodname_GH_advanced_security %}," next to "Committers", click **{% octicon "download" aria-hidden="true" %} CSV report**.
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghas-billing-table-ui-update %}
|
||||
|
|
|
|||
|
|
@ -33,7 +33,7 @@ The spending information will display the total spending for each organization f
|
|||
{% endif %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-label="The credit card icon" %} Billing and plans**.
|
||||
1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing and plans**.
|
||||
1. Under "{% data variables.product.prodname_copilot_short %}", view the breakdown of your {% data variables.product.prodname_copilot %} usage and upcoming changes in your organization.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -34,7 +34,7 @@ To connect your Azure subscription, you must have owner permissions to the subsc
|
|||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-label="The credit card icon" %} Billing and plans**.
|
||||
1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing and plans**.
|
||||
1. Under "Billing Management", to the right of "Metered billing via Azure", click **Add Azure Subscription**.
|
||||
1. To sign in to your Microsoft account, follow the prompts.
|
||||
1. Review the "Permissions requested" prompt. If you agree with the terms, click **Accept**.
|
||||
|
|
@ -77,7 +77,7 @@ After you disconnect your Azure subscription from your organization account, you
|
|||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-label="The credit card icon" %} Billing and plans**.
|
||||
1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing and plans**.
|
||||
1. Under "Billing Management", then under "Metered billing via Azure", to the right of the subscription ID you want to disconnect, click **{% octicon "trash" aria-label="The trash icon" %}**.
|
||||
1. Review the prompt, then click **Remove**.
|
||||
|
||||
|
|
|
|||
|
|
@ -38,10 +38,10 @@ If you're an organization or enterprise owner, you can switch between settings f
|
|||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
1. At the top of the page, to the right of your name, click **Switch to another account**.
|
||||
|
||||
|
||||
|
||||
1. Start typing the name of the account you want to switch to, then click the name of the account.
|
||||
1. In the left sidebar, click **{% octicon "credit-card" aria-label="The credit card icon" %} Billing and plans**.
|
||||
1. In the left sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing and plans**.
|
||||
|
||||
## Further reading
|
||||
|
||||
|
|
|
|||
|
|
@ -41,7 +41,7 @@ After you enable {% data variables.product.prodname_github_connect %}, license d
|
|||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.license-tab %}
|
||||
1. Under "License sync", click {% octicon "sync" aria-label="The Sync icon" %} **Sync now**.
|
||||
1. Under "License sync", click {% octicon "sync" aria-hidden="true" %} **Sync now**.
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
|
|
|||
|
|
@ -74,9 +74,9 @@ You can create {% data variables.product.prodname_codeql %} debugging artifacts
|
|||
|
||||
If your {% data variables.product.prodname_code_scanning %} results are different than you expected, your repository may have both default and advanced {% data variables.product.prodname_code_scanning %} setups. When you enable default setup, this disables the existing {% data variables.product.prodname_codeql %} workflow file and blocks any {% data variables.product.prodname_codeql %} API analysis from uploading results.
|
||||
|
||||
To check if default setup is enabled, navigate to the main page of the repository, then click {% octicon "gear" aria-label="The gear icon" %} **Settings**. In the "Security" section of the sidebar, click {% octicon "codescan" aria-label="The {% data variables.product.prodname_code_scanning %} icon" %} **Code security and analysis**. In the "{% data variables.product.prodname_code_scanning_caps %}" section of the page, next to "{% data variables.product.prodname_codeql %} analysis," click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. If there is a {% octicon "workflow" aria-label="The workflow icon" %} **Switch to advanced** option, you are currently using the default setup.
|
||||
To check if default setup is enabled, navigate to the main page of the repository, then click {% octicon "gear" aria-hidden="true" %} **Settings**. In the "Security" section of the sidebar, click {% octicon "codescan" aria-hidden="true" %} **Code security and analysis**. In the "{% data variables.product.prodname_code_scanning_caps %}" section of the page, next to "{% data variables.product.prodname_codeql %} analysis," click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. If there is a {% octicon "workflow" aria-hidden="true" %} **Switch to advanced** option, you are currently using the default setup.
|
||||
|
||||
If you want to return to using advanced setup and get {% data variables.product.prodname_code_scanning %} results from your custom workflow file, click {% octicon "stop" aria-label="The stop icon" %} **Disable {% data variables.product.prodname_codeql %}** to disable default setup. Then you should re-enable your pre-existing workflows to start triggering and uploading results from advanced setup. For more information, see "[AUTOTITLE](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)" and "[AUTOTITLE](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning-for-a-repository#creating-an-advanced-setup)."
|
||||
If you want to return to using advanced setup and get {% data variables.product.prodname_code_scanning %} results from your custom workflow file, click {% octicon "stop" aria-hidden="true" %} **Disable {% data variables.product.prodname_codeql %}** to disable default setup. Then you should re-enable your pre-existing workflows to start triggering and uploading results from advanced setup. For more information, see "[AUTOTITLE](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)" and "[AUTOTITLE](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning-for-a-repository#creating-an-advanced-setup)."
|
||||
|
||||
{% ifversion remove-code-scanning-configurations %}
|
||||
{% data reusables.code-scanning.troubleshooting-multiple-configurations %}
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ topics:
|
|||
- Troubleshooting
|
||||
---
|
||||
|
||||
## A pre-existing {% data variables.product.prodname_codeql %} workflow is disabled
|
||||
## A pre-existing {% data variables.product.prodname_codeql %} workflow is disabled
|
||||
|
||||
If you see two workflows named **{% data variables.product.prodname_codeql %}**, one workflow may be a pre-existing {% data variables.product.prodname_codeql %} workflow file which has been disabled by default setup. Default setup overrides existing {% data variables.product.prodname_codeql %} setups by disabling any existing {% data variables.product.prodname_codeql %} workflows, and blocking any {% data variables.product.prodname_codeql %} analysis API uploads. This behavior stops you using {% data variables.product.prodname_actions %} minutes to run workflows for {% data variables.product.prodname_codeql %} advanced setup when only the results from default setup will be used. For more information about switching between advanced and default setups, see "[AUTOTITLE](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow#results-are-different-than-expected)."
|
||||
|
||||
|
|
@ -24,7 +24,7 @@ Optionally, if you are certain you no longer need the pre-existing workflow file
|
|||
|
||||
## Enabling the default setup takes too long
|
||||
|
||||
If enabling your default setup is taking too long, try canceling the workflow run and restarting the setup. To restart your setup, navigate to the main page of your repository, then click {% octicon "play" aria-label="The play icon" %} **Actions**. Click the **{% data variables.product.prodname_codeql %}** workflow run that's in progress, then click **Cancel workflow**. Once {% octicon "stop" aria-label="The stop icon" %} appears beside the workflow run name, navigate back to the **Code security and analysis** settings and re-enable the default setup. If the default setup continues to stall, please contact {% data variables.contact.contact_support %} or try enabling the advanced setup. For more information, see "[AUTOTITLE](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning-for-a-repository#creating-an-advanced-setup)."
|
||||
If enabling your default setup is taking too long, try canceling the workflow run and restarting the setup. To restart your setup, navigate to the main page of your repository, then click {% octicon "play" aria-hidden="true" %} **Actions**. Click the **{% data variables.product.prodname_codeql %}** workflow run that's in progress, then click **Cancel workflow**. Once {% octicon "stop" aria-label="The stop icon" %} appears beside the workflow run name, navigate back to the **Code security and analysis** settings and re-enable the default setup. If the default setup continues to stall, please contact {% data variables.contact.contact_support %} or try enabling the advanced setup. For more information, see "[AUTOTITLE](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning-for-a-repository#creating-an-advanced-setup)."
|
||||
|
||||
## Unclear what triggered a workflow run
|
||||
|
||||
|
|
|
|||
|
|
@ -78,7 +78,6 @@ After configuring {% data variables.product.prodname_code_scanning %} for your r
|
|||
|
||||
1. Review the logging output from the actions in this workflow as they run.
|
||||
|
||||
1. Optionally, to see more detail about the commit that triggered the workflow run, click {% octicon "git-commit" aria-label="The commit icon" %} **SHORT COMMIT HASH**. This short commit hash is 7 lowercase characters immediately following the commit author's username.
|
||||
1. Optionally, to see more detail about the commit that triggered the workflow run, click the short commit hash. The short commit hash is 7 lowercase characters immediately following the commit author's username.
|
||||
|
||||
1. Once all jobs are complete, you can view the details of any {% data variables.product.prodname_code_scanning %} alerts that were identified. For more information, see "[AUTOTITLE](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)."
|
||||
|
||||
|
|
|
|||
|
|
@ -111,8 +111,8 @@ You can configure {% data variables.product.prodname_code_scanning %} to automat
|
|||
|
||||
{% ifversion code-scanning-without-workflow %}
|
||||
|
||||
1. From the main page of your repository, click {% octicon "gear" aria-label="The gear icon" %} **Settings**.
|
||||
1. In the "Security" section of the sidebar, click **{% octicon "shield-lock" aria-label="The shield-lock icon" %} Code security and analysis**.
|
||||
1. From the main page of your repository, click {% octicon "gear" aria-hidden="true" %} **Settings**.
|
||||
1. In the "Security" section of the sidebar, click **{% octicon "shield-lock" aria-hidden="true" %} Code security and analysis**.
|
||||
1. In the "{% data variables.product.prodname_code_scanning_caps %}" section, select **Set up** {% octicon "triangle-down" aria-label="The downwards-facing triangle icon" %}, then click **Default**.
|
||||
1. In the pop-up window that appears, review the default configuration settings for your repository, then click **Enable {% data variables.product.prodname_codeql %}**.
|
||||
|
||||
|
|
|
|||
|
|
@ -77,7 +77,7 @@ shortTitle: Manage secret alerts
|
|||
|
||||
{% endnote %}
|
||||
|
||||
In the view for an active {% data variables.product.company_short %} token alert, you can review certain metadata about the token. This metadata may help you identify the token and decide what remediation steps to take. For more information on viewing individual alerts, see "[Managing {% data variables.product.prodname_secret_scanning %} alerts](#managing-secret-scanning-alerts)."
|
||||
In the view for an active {% data variables.product.company_short %} token alert, you can review certain metadata about the token. This metadata may help you identify the token and decide what remediation steps to take. For more information on viewing individual alerts, see "[Managing {% data variables.product.prodname_secret_scanning %} alerts](#managing-secret-scanning-alerts)."
|
||||
|
||||
Tokens, like {% data variables.product.pat_generic %} and other credentials, are considered personal information. For more information about using {% data variables.product.company_short %} tokens, see [GitHub's Privacy Statement](/free-pro-team@latest/site-policy/privacy-policies/github-privacy-statement) and [Acceptable Use Policies](/free-pro-team@latest/site-policy/acceptable-use-policies/github-acceptable-use-policies).
|
||||
|
||||
|
|
@ -120,7 +120,7 @@ Once a secret has been committed to a repository, you should consider the secret
|
|||
|
||||
{% ifversion secret-scanning-notification-settings %}
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
1. To start watching the repository, select **{% octicon "eye" aria-label="The Eye icon" %}Watch**.
|
||||
1. To start watching the repository, select **{% octicon "eye" aria-hidden="true" %} Watch**.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -80,7 +80,7 @@ You may have a codespace that you want to keep for longer than the retention per
|
|||
Codespaces incur storage costs, or consume your included storage allowance if the codespace is owned by your personal {% data variables.product.prodname_dotcom %} account. You should therefore be aware of the cost implications of storing codespaces indefinitely. For more information, see "[AUTOTITLE](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#about-billing-for-storage-usage)."
|
||||
|
||||
{% data reusables.codespaces.your-codespaces-procedure-step %}
|
||||
1. To the right of the codespace you want to exempt from automatic deletion, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **{% octicon "bookmark" aria-label="The bookmark icon" %} Keep codespace**.
|
||||
1. To the right of the codespace you want to exempt from automatic deletion, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **{% octicon "bookmark" aria-hidden="true" %} Keep codespace**.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -74,7 +74,7 @@ If you want to use Git hooks for your codespace, then you should set up hooks us
|
|||
|
||||
|
||||
|
||||
1. Click the **{% octicon "code" aria-label="The code icon" %} Code** button, then click the **Codespaces** tab.
|
||||
1. Click the **{% octicon "code" aria-hidden="true" %} Code** button, then click the **Codespaces** tab.
|
||||
|
||||
If codespaces for this repository are billable to an organization, or its parent enterprise, a message is displayed below the **Create codespace on BRANCH** button telling you who will pay for the codespace.
|
||||
|
||||
|
|
@ -114,16 +114,16 @@ If you want to use Git hooks for your codespace, then you should set up hooks us
|
|||
|
||||
## Recommended secrets
|
||||
|
||||
The names of user-defined secrets may be displayed on the advanced options page when you create a codespace. This will happen if recommended secrets have been specified in the dev container configuration you have selected.
|
||||
|
||||
The names of user-defined secrets may be displayed on the advanced options page when you create a codespace. This will happen if recommended secrets have been specified in the dev container configuration you have selected.
|
||||
|
||||
<img src="/assets/images/help/codespaces/recommended-secrets.png" style="max-height:50rem" alt='Screenshot of the "Create codespace" page with four recommended secrets highlighted with a dark orange outline.' />
|
||||
|
||||
Entering values for these secrets, when you're prompted to do so, is recommended because it's likely your project will need values for these secrets. However, supplying values is not required for you to create a codespace. You can set these secrets within the codespace if you prefer.
|
||||
|
||||
If you enter a value for a recommended secret, the secret will available in the new codespace. When you click **Create codespace**, the secret is also added to your personal settings for {% data variables.product.prodname_codespaces %}, so you will not need to enter a value for the secret in future when you create a codespace for this repository.
|
||||
|
||||
|
||||
If the name of a secret is shown with a checkbox that is unavailable for selection, and no input box, this is because you already have a secret of this name configured in your personal settings for {% data variables.product.prodname_codespaces %}, and you have associated it with this repository. If you've created a secret of this name but have not associated it with this repository, the checkbox will be available to select and by doing so you can update your settings to add the association.
|
||||
|
||||
|
||||
If you want to change the value of a preselected secret you can do so from your personal settings for {% data variables.product.prodname_codespaces %} at [github.com/settings/codespaces](https://github.com/settings/codespaces). For more information, see "[AUTOTITLE](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)."
|
||||
|
||||
{% endwebui %}
|
||||
|
|
|
|||
|
|
@ -63,7 +63,7 @@ You can create a codespace from any template repository, then publish your work
|
|||
|
||||
{% note %}
|
||||
|
||||
**Note:** If you're a maintainer of the template repository, and want to commit changes to the template repository itself, you should create a codespace from the **{% octicon "code" aria-label="The code icon" %} Code** dropdown. For more information, see "[AUTOTITLE](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)."
|
||||
**Note:** If you're a maintainer of the template repository, and want to commit changes to the template repository itself, you should create a codespace from the **{% octicon "code" aria-hidden="true" %} Code** dropdown. For more information, see "[AUTOTITLE](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
|
|
|
|||
|
|
@ -43,7 +43,7 @@ There are costs associated with storing codespaces. You should therefore delete
|
|||
{% webui %}
|
||||
|
||||
{% data reusables.codespaces.your-codespaces-procedure-step %}
|
||||
1. To the right of the codespace you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **{% octicon "trash" aria-label="The trash icon" %} Delete**.
|
||||
1. To the right of the codespace you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **{% octicon "trash" aria-hidden="true" %} Delete**.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ redirect_from:
|
|||
{% data reusables.repositories.sidebar-pr %}
|
||||
|
||||
1. In the list of pull requests, click the pull request you'd like to open in {% data variables.product.prodname_codespaces %}.
|
||||
1. On the right-hand side of your screen, click **{% octicon "code" aria-label="The code icon" %} Code**.
|
||||
1. On the right-hand side of your screen, click **{% octicon "code" aria-hidden="true" %} Code**.
|
||||
1. In the {% data variables.product.prodname_codespaces %} tab, click the plus sign ({% octicon "plus" aria-label="The plus icon" %})
|
||||
|
||||
|
||||
|
|
@ -67,4 +67,4 @@ For more information on reviewing a pull request, see "[AUTOTITLE](/pull-request
|
|||
|
||||
## View comments from a review in {% data variables.product.prodname_codespaces %}
|
||||
|
||||
Once you have received feedback on a pull request, you can [open it in a codespace](#opening-a-pull-request-in-codespaces) in your web browser, or in {% data variables.product.prodname_vscode_shortname %}, to see the [review comments](#reviewing-a-pull-request-in-codespaces). From there you can respond to comments, add reactions, or dismiss the review.
|
||||
Once you have received feedback on a pull request, you can [open it in a codespace](#opening-a-pull-request-in-codespaces) in your web browser, or in {% data variables.product.prodname_vscode_shortname %}, to see the [review comments](#reviewing-a-pull-request-in-codespaces). From there you can respond to comments, add reactions, or dismiss the review.
|
||||
|
|
|
|||
|
|
@ -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-label="The zap icon" %} 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-label="The history icon" %} Prebuild in progress" label. For more information, see "[AUTOTITLE](/codespaces/developing-in-codespaces/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-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)."
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -181,7 +181,7 @@ If none of the predefined configurations meets your needs, you can create a cust
|
|||
### Adding a `devcontainer.json` file
|
||||
|
||||
If you don't already have a `devcontainer.json` file in your repository, you can quickly add one from {% data variables.product.prodname_dotcom_the_website %}.
|
||||
1. Navigate to your repository and click the **{% octicon "code" aria-label="The code icon" %} Code** dropdown.
|
||||
1. Navigate to your repository and click the **{% octicon "code" aria-hidden="true" %} Code** dropdown.
|
||||
1. In the **Codespaces** tab, click the ellipsis (**...**), then select **Configure dev container**.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -45,7 +45,7 @@ You can use the "Share a deep link" option to configure more options for the cod
|
|||
|
||||
|
||||
|
||||
1. Click the **{% octicon "code" aria-label="The code icon" %} Code** button, then click the **Codespaces** tab.
|
||||
1. Click the **{% octicon "code" aria-hidden="true" %} Code** button, then click the **Codespaces** tab.
|
||||
1. To open the "Share codespace configuration" window, at the top right of the **Codespaces** tab, select {% octicon "kebab-horizontal" aria-label="Codespace repository configuration" %}, then click **Share a deep link**.
|
||||
|
||||
|
||||
|
|
@ -60,7 +60,7 @@ You can use the "Share a deep link" option to configure more options for the cod
|
|||
|
||||
You can create a link to a page for resuming your most recent codespace that matches the repository, branch, and other options specified in the URL.
|
||||
|
||||
Add `?quickstart=1` to a `codespaces.new` URL, such as the URLs listed in the previous section of this article. This produces a URL that displays a "Resume codespace" page.
|
||||
Add `?quickstart=1` to a `codespaces.new` URL, such as the URLs listed in the previous section of this article. This produces a URL that displays a "Resume codespace" page.
|
||||
|
||||
For example, the URL `https://codespaces.new/octo-org/octo-repo?quickstart=1` opens a page to allow you to resume your most recent codespace for the default branch of the `octo-org/octo-repo` repository.
|
||||
|
||||
|
|
@ -68,7 +68,7 @@ For example, the URL `https://codespaces.new/octo-org/octo-repo?quickstart=1` op
|
|||
|
||||
{% note %}
|
||||
|
||||
**Notes**:
|
||||
**Notes**:
|
||||
|
||||
- If the `codespaces.new` URL already contains a query string, add `&quickstart=1` at the end of the query string.
|
||||
- This type of URL will always open a codespace in the {% data variables.product.prodname_vscode_shortname %} web client, even if this is not set as your default editor for {% data variables.product.prodname_github_codespaces %}.
|
||||
|
|
@ -101,5 +101,5 @@ This type of URL is useful, for instance, in a README for your repository as it
|
|||
```
|
||||
|
||||
The example Markdown is rendered like this:
|
||||
|
||||
|
||||
[](https://codespaces.new/github/docs)
|
||||
|
|
@ -12,7 +12,7 @@ shortTitle: Exporting changes
|
|||
|
||||
## About exporting changes
|
||||
|
||||
While using {% data variables.product.prodname_github_codespaces %}, you may want to export your changes to a branch without launching your codespace. This can be useful when you have hit a [spending limit](/billing/managing-billing-for-github-codespaces/managing-the-spending-limit-for-github-codespaces) or have a general issue accessing your codespace.
|
||||
While using {% data variables.product.prodname_github_codespaces %}, you may want to export your changes to a branch without launching your codespace. This can be useful when you have hit a [spending limit](/billing/managing-billing-for-github-codespaces/managing-the-spending-limit-for-github-codespaces) or have a general issue accessing your codespace.
|
||||
|
||||
You can export your changes in one of several ways, depending on how you created the codespace. In every case, only the Git branch that is currently checked out in the codespace is exported. Work contained in other branches is not exported.
|
||||
|
||||
|
|
@ -24,7 +24,7 @@ You can export your changes in one of several ways, depending on how you created
|
|||
|
||||
The following steps describe how to export your changes to a branch or fork. For information on exporting an unpublished codespace to a new repository, see "[AUTOTITLE](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template#publishing-from-githubcom)."
|
||||
|
||||
{% data reusables.codespaces.your-codespaces-procedure-step %} Or, for an individual repository, click the **{% octicon "code" aria-label="The code icon" %} Code** menu.
|
||||
{% data reusables.codespaces.your-codespaces-procedure-step %} Or, for an individual repository, click the **{% octicon "code" aria-hidden="true" %} Code** menu.
|
||||
1. Click the ellipsis (**...**) to the right of the codespace you want to export from.
|
||||
1. Select **{% octicon "git-branch" aria-hidden="true" %} Export changes to a branch** or **{% octicon "git-branch" aria-hidden="true" %} Export changes to a fork**.
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ For more information about {% data variables.product.prodname_github_codespaces
|
|||
|
||||
## Checking whether a codespace was created from a prebuild?
|
||||
|
||||
When you create a codespace, you can choose the type of the virtual machine you want to use. If a prebuild is available for the type of virtual machine, "{% octicon "zap" aria-label="The zap icon" %} Prebuild ready" is shown next to it.
|
||||
When you create a codespace, you can choose the type of the virtual machine you want to use. If a prebuild is available for the type of virtual machine, "{% octicon "zap" aria-hidden="true" %} Prebuild ready" is shown next to it.
|
||||
|
||||
|
||||
|
||||
|
|
@ -46,18 +46,18 @@ You can check how much storage space has been consumed by prebuilds in your curr
|
|||
|
||||
## The "Prebuild Ready" label is sometimes missing
|
||||
|
||||
You may notice that sometimes, when you create a new codespace from a prebuild-enabled branch, the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is not displayed in the dialog box for choosing a machine type. This means that prebuilds are not currently available.
|
||||
You may notice that sometimes, when you create a new codespace from a prebuild-enabled branch, the "{% octicon "zap" aria-hidden="true" %} Prebuild Ready" label is not displayed in the dialog box for choosing a machine type. This means that prebuilds are not currently available.
|
||||
|
||||
By default, each time you push to a prebuild-enabled branch, the prebuild is updated. If the push involves a change to the dev container configuration then, while the update is in progress, the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is removed from the list of machine types. During this time you can still create codespaces without a prebuild. If required, you can reduce the occasions on which prebuilds are unavailable for a repository by setting the prebuild to be updated only when you make a change to your dev container configuration files, or only on a custom schedule. For more information, see "[AUTOTITLE](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds)."
|
||||
By default, each time you push to a prebuild-enabled branch, the prebuild is updated. If the push involves a change to the dev container configuration then, while the update is in progress, the "{% octicon "zap" aria-hidden="true" %} Prebuild Ready" label is removed from the list of machine types. During this time you can still create codespaces without a prebuild. If required, you can reduce the occasions on which prebuilds are unavailable for a repository by setting the prebuild to be updated only when you make a change to your dev container configuration files, or only on a custom schedule. For more information, see "[AUTOTITLE](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds)."
|
||||
|
||||
If your branch is not specifically enabled for prebuilds it may still benefit from prebuilds if it was branched from a prebuild-enabled branch. However, if the dev container configuration is changed on your branch, so that it's not the same as the configuration on the base branch, prebuilds will no longer be available on your branch.
|
||||
|
||||
Here are things to check if the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is not displayed for a particular branch:
|
||||
Here are things to check if the "{% octicon "zap" aaria-hidden="true" %} Prebuild Ready" label is not displayed for a particular branch:
|
||||
|
||||
* Confirm that a prebuild configuration exists for this branch. If you’re not a repository administrator, you'll need to reach out to one to confirm this.
|
||||
* Confirm that the prebuild configuration includes your region.
|
||||
* Check whether a change to the dev container configuration was pushed to the prebuild-enabled branch recently. If so, you will typically have to wait until the prebuild workflow run for this push completes before prebuilds are available again.
|
||||
* If no configuration changes were recently made, go to the **Actions** tab of your repository, click **{% octicon "codespaces" aria-label="The Codespaces icon" %} {% data variables.product.prodname_codespaces %} Prebuilds** in the workflows list, and check that prebuild workflow runs for the branch are succeeding. If latest runs of a workflow failed, and one or more of these failed runs contained changes to the dev container configuration, then there will be no available prebuilds for the associated branch.
|
||||
* If no configuration changes were recently made, go to the **Actions** tab of your repository, click **{% octicon "codespaces" aria-hidden="true" %} {% data variables.product.prodname_codespaces %} Prebuilds** in the workflows list, and check that prebuild workflow runs for the branch are succeeding. If latest runs of a workflow failed, and one or more of these failed runs contained changes to the dev container configuration, then there will be no available prebuilds for the associated branch.
|
||||
|
||||
## Some resources cannot be accessed in codespaces created using a prebuild
|
||||
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ Depending on the policy settings configured at the enterprise level, an organiza
|
|||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "copilot" aria-label="The copilot icon" %} {% data variables.product.prodname_copilot_short %}**, and then click **Access**.
|
||||
1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "copilot" aria-hidden="true" %} {% data variables.product.prodname_copilot_short %}**, and then click **Access**.
|
||||
1. Under "User permissions," to enable {% data variables.product.prodname_copilot %} for all current and future users in your organization, select **Purchase for all members**.
|
||||
1. In the "Confirm seat assignment" dialog, to confirm that you want to enable {% data variables.product.prodname_copilot %} for all current and future users in your organization, click **Confirm**.
|
||||
1. To save your changes, click **Save**.
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@ Some workflows require or benefit from rebasing instead of merging. By rebasing
|
|||
|
||||
## Pulling to your local branch from the remote
|
||||
|
||||
1. In {% data variables.product.prodname_desktop %}, use the {% octicon "git-branch" aria-label="The branch icon" %} **Current Branch** drop-down, and select the local branch you want to update.
|
||||
1. In {% data variables.product.prodname_desktop %}, use the {% octicon "git-branch" aria-hidden="true" %} **Current Branch** drop-down, and select the local branch you want to update.
|
||||
2. To check for commits on the remote branch, click **Fetch origin**
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ shortTitle: Commit & review changes
|
|||
|
||||
## Choosing a branch and making changes
|
||||
|
||||
1. [Create a new branch](/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches-in-github-desktop), or select an existing branch by clicking {% octicon "git-branch" aria-label="The branch icon" %} **Current Branch** on the toolbar and selecting the branch from the list.
|
||||
1. [Create a new branch](/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches-in-github-desktop), or select an existing branch by clicking {% octicon "git-branch" aria-hidden="true" %} **Current Branch** on the toolbar and selecting the branch from the list.
|
||||
|
||||
|
||||
{% data reusables.desktop.make-changes %}
|
||||
|
|
@ -118,7 +118,6 @@ Once you're satisfied with the changes you've chosen to include in your commit,
|
|||
|
||||
6. If you have a pull request based off the branch you are working on, {% data variables.product.prodname_desktop %} will display the status of the checks that have run for the pull request next to the "Current Branch" section of the repository bar. For more information about checks, see "[AUTOTITLE](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop)."
|
||||
|
||||
|
||||
If a pull request has not been created for the current branch, {% data variables.product.prodname_desktop %} will give you the option to preview the changes and create one. For more information, see "[AUTOTITLE](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request-from-github-desktop)."
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -59,7 +59,7 @@ You can always create a branch in {% data variables.product.prodname_desktop %}
|
|||
|
||||
If you create a branch on {% data variables.product.product_name %}, you'll need to publish the branch to make it available for collaboration on {% data variables.product.prodname_dotcom %}.
|
||||
|
||||
1. In the repository bar, click {% octicon "git-branch" aria-label="The branch icon" %} **Current Branch**, then click the branch that you want to publish.
|
||||
1. In the repository bar, click {% octicon "git-branch" aria-hidden="true" %} **Current Branch**, then click the branch that you want to publish.
|
||||
|
||||
2. Click **Publish branch**.
|
||||
|
||||
|
|
@ -73,7 +73,7 @@ You can view and make commits to any of your repository's branches. If you have
|
|||
|
||||
{% endtip %}
|
||||
|
||||
1. In the repository bar, click {% octicon "git-branch" aria-label="The branch icon" %} **Current Branch**, then click the branch that you want to switch to.
|
||||
1. In the repository bar, click {% octicon "git-branch" aria-hidden="true" %} **Current Branch**, then click the branch that you want to switch to.
|
||||
|
||||
1. If you have saved, uncommitted changes, in the "Switch Branch" window, select **Leave my changes on CURRENT-BRANCH** or **Bring my changes to NEW-BRANCH**, then click **Switch Branch**.
|
||||
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ You can also use cherry-picking when collaborating with a team. Some projects in
|
|||
|
||||
|
||||
{% data reusables.desktop.history-tab %}
|
||||
4. Drag the commit that you want to cherry-pick from the "History" tab to the {% octicon "git-branch" aria-label="The branch icon" %} **Current Branch** dropdown menu, then drop the commit on the branch that you want to copy the commit to.
|
||||
4. Drag the commit that you want to cherry-pick from the "History" tab to the {% octicon "git-branch" aria-hidden="true" %} **Current Branch** dropdown menu, then drop the commit on the branch that you want to copy the commit to.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ versions:
|
|||
4. Click on the pull request number, to the right of the pull request branch name.
|
||||
|
||||
|
||||
5. To re-run failed checks, click **{% octicon "sync" aria-label="The sync icon" %} Re-run** and select **Re-run Failed Checks**.
|
||||
5. To re-run failed checks, click **{% octicon "sync" aria-hidden="true" %} Re-run** and select **Re-run Failed Checks**.
|
||||
|
||||
|
||||
6. To re-run individual checks, hover over the individual check you want to re-run and select the {% octicon "sync" aria-label="The sync icon" %} icon to re-run the check.
|
||||
|
|
|
|||
|
|
@ -62,7 +62,7 @@ You can pin up to four important discussions above the list of discussions for t
|
|||
{% data reusables.discussions.navigate-to-repo-or-org %}
|
||||
{% data reusables.discussions.discussions-tab %}
|
||||
{% data reusables.discussions.click-discussion-in-list %}
|
||||
1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Pin discussion**.
|
||||
1. In the right sidebar, click {% octicon "pin" aria-hidden="true" %} **Pin discussion**.
|
||||
{% ifversion discussions-category-specific-pins %}
|
||||
|
||||
{% else %}
|
||||
|
|
@ -80,7 +80,7 @@ You can pin up to four important discussions above the list of discussions in a
|
|||
{% data reusables.discussions.navigate-to-repo-or-org %}
|
||||
{% data reusables.discussions.discussions-tab %}
|
||||
{% data reusables.discussions.click-discussion-in-list %}
|
||||
1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Pin discussion to CATEGORY**.
|
||||
1. In the right sidebar, click {% octicon "pin" aria-hidden="true" %} **Pin discussion to CATEGORY**.
|
||||
|
||||
|
||||
|
||||
|
|
@ -94,7 +94,7 @@ Editing a pinned discussion will not change the discussion's category. For more
|
|||
{% data reusables.discussions.navigate-to-repo-or-org %}
|
||||
{% data reusables.discussions.discussions-tab %}
|
||||
{% data reusables.discussions.click-discussion-in-list %}
|
||||
1. In the right sidebar, click {% octicon "pencil" aria-label="The pencil icon" %} **Edit pinned discussion**. {% ifversion discussions-category-specific-pins %}
|
||||
1. In the right sidebar, click {% octicon "pencil" aria-hidden="true" %} **Edit pinned discussion**. {% ifversion discussions-category-specific-pins %}
|
||||
|
||||
{% endif %}
|
||||
1. Customize the look of the pinned discussion.
|
||||
|
|
@ -114,7 +114,7 @@ You can unpin a globally pinned discussion. This will not delete the discussion,
|
|||
{% data reusables.discussions.navigate-to-repo-or-org %}
|
||||
{% data reusables.discussions.discussions-tab %}
|
||||
{% data reusables.discussions.click-discussion-in-list %}
|
||||
1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Unpin discussion**.
|
||||
1. In the right sidebar, click {% octicon "pin" aria-hidden="true" %} **Unpin discussion**.
|
||||
|
||||
|
||||
|
||||
|
|
@ -128,7 +128,7 @@ You can unpin a discussion pinned to a specific category. This will not delete t
|
|||
{% data reusables.discussions.navigate-to-repo-or-org %}
|
||||
{% data reusables.discussions.discussions-tab %}
|
||||
{% data reusables.discussions.click-discussion-in-list %}
|
||||
1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Unpin discussion from this category**.
|
||||
1. In the right sidebar, click {% octicon "pin" aria-hidden="true" %} **Unpin discussion from this category**.
|
||||
|
||||
|
||||
|
||||
|
|
@ -142,7 +142,7 @@ To transfer a discussion, you must have permissions to create discussions in the
|
|||
{% data reusables.discussions.navigate-to-repo-or-org %}
|
||||
{% data reusables.discussions.discussions-tab %}
|
||||
{% data reusables.discussions.click-discussion-in-list %}
|
||||
1. In the right sidebar, click {% octicon "arrow-right" aria-label="The right arrow icon" %} {% ifversion discussions-category-specific-pins %}**Transfer this discussion**{% else %}**Transfer discussion**{% endif %}.
|
||||
1. In the right sidebar, click {% octicon "arrow-right" aria-hidden="true" %} {% ifversion discussions-category-specific-pins %}**Transfer this discussion**{% else %}**Transfer discussion**{% endif %}.
|
||||
{% ifversion discussions-category-specific-pins %}
|
||||
|
||||
 {% else %}
|
||||
|
|
@ -157,7 +157,7 @@ To transfer a discussion, you must have permissions to create discussions in the
|
|||
{% data reusables.discussions.navigate-to-repo-or-org %}
|
||||
{% data reusables.discussions.discussions-tab %}
|
||||
{% data reusables.discussions.click-discussion-in-list %}
|
||||
1. In the right sidebar, click {% octicon "trash" aria-label="The trash arrow icon" %} **Delete discussion**.
|
||||
1. In the right sidebar, click {% octicon "trash" aria-hidden="true" %} **Delete discussion**.
|
||||
{% ifversion discussions-category-specific-pins %}
|
||||
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ You can star repositories listed in the {% data variables.product.prodname_commu
|
|||
|
||||
Repository listings in the {% data variables.product.prodname_community_exchange %} gallery can be sorted on the number of stars a repository has.
|
||||
|
||||
To star a repository: Go to your {% data variables.product.prodname_community_exchange %} home page, find the repository you want to star, and click {% octicon "star" aria-label="The star icon" %} **Star** button found right by its name.
|
||||
To star a repository: Go to your {% data variables.product.prodname_community_exchange %} home page, find the repository you want to star, and click {% octicon "star" aria-hidden="true" %} **Star** button found right by its name.
|
||||
|
||||
## Reporting abuse
|
||||
|
||||
|
|
|
|||
|
|
@ -78,7 +78,7 @@ If you use a template repository for an assignment, you can define a dev contain
|
|||
|
||||
When a student opens an assignment, the repository's README file includes their teacher's recommendation of the IDE they should use for the work.
|
||||
|
||||
Students can launch a new or existing codespace by clicking the **Open in GitHub Codespace** button in the README, or by clicking the **{% octicon "code" aria-label="The code icon" %} Code** button on the main page of the assignment repository, then selecting the **Codespaces** tab. From the **Codespaces** tab you can select an existing codespace or create a new one. For more information, see "[AUTOTITLE](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)."
|
||||
Students can launch a new or existing codespace by clicking the **Open in GitHub Codespace** button in the README, or by clicking the **{% octicon "code" aria-hidden="true" %} Code** button on the main page of the assignment repository, then selecting the **Codespaces** tab. From the **Codespaces** tab you can select an existing codespace or create a new one. For more information, see "[AUTOTITLE](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)."
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ After creating an assignment, you can edit many aspects of the assignment to bet
|
|||
|
||||
{% data reusables.classroom.sign-into-github-classroom %}
|
||||
{% data reusables.classroom.click-classroom-in-list %}
|
||||
1. In the {% octicon "repo" aria-label="The repo icon" %} **Assignments** tab, next to the assignment you would like to edit, click {% octicon "pencil" aria-label="The pencil icon" %}.
|
||||
1. In the {% octicon "repo" aria-hidden="true" %} **Assignments** tab, next to the assignment you would like to edit, click {% octicon "pencil" aria-label="The pencil icon" %}.
|
||||
|
||||
{% note %}
|
||||
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ The copied assignment includes assignment details such as the name, source repos
|
|||
1. Sign into {% data variables.product.prodname_classroom_with_url %}.
|
||||
1. Navigate to the classroom that has the assignment that you want to reuse.
|
||||
1. In the list of assignments, click the assignment you want to reuse.
|
||||
1. Select the **{% octicon "pencil" aria-label="The pencil icon" %} Edit** dropdown menu in the top right of the page, then click **{% octicon "sync" aria-label="The sync icon" %} Reuse assignment**.
|
||||
1. Select the **{% octicon "pencil" aria-hidden="true" %} Edit** dropdown menu in the top right of the page, then click **{% octicon "sync" aria-hidden="true" %} Reuse assignment**.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ The Git & {% data variables.product.company_short %} starter assignment is a pre
|
|||
|
||||
1. Sign into {% data variables.product.prodname_classroom_with_url %}.
|
||||
1. Navigate to a classroom.
|
||||
1. In the {% octicon "repo" aria-label="The repo icon" %} **Assignments** tab, click the link in the blue banner.
|
||||
1. In the {% octicon "repo" aria-hidden="true" %} **Assignments** tab, click the link in the blue banner.
|
||||
|
||||
## Setting up the basics for an assignment
|
||||
|
||||
|
|
|
|||
|
|
@ -55,11 +55,11 @@ During the beta for {% data variables.product.prodname_mobile %} with {% data va
|
|||
|
||||
### Adding, switching, or signing out of accounts
|
||||
|
||||
You can sign into mobile with a personal account on {% data variables.product.prodname_ghe_server %}. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap {% octicon "plus" aria-label="The plus icon" %} **Add Enterprise Account**. Follow the prompts to sign in.
|
||||
You can sign into mobile with a personal account on {% data variables.product.prodname_ghe_server %}. At the bottom of the app, long-press {% octicon "person" aria-hidden="true" %} **Profile**, then tap {% octicon "plus" aria-hidden="true" %} **Add Enterprise Account**. Follow the prompts to sign in.
|
||||
|
||||
After you sign into mobile with a personal account on {% data variables.product.prodname_ghe_server %}, you can switch between the account and your account on {% data variables.product.prodname_dotcom_the_website %}. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap the account you want to switch to.
|
||||
After you sign into mobile with a personal account on {% data variables.product.prodname_ghe_server %}, you can switch between the account and your account on {% data variables.product.prodname_dotcom_the_website %}. At the bottom of the app, long-press {% octicon "person" aria-hidden="true" %} **Profile**, then tap the account you want to switch to.
|
||||
|
||||
If you no longer need to access data for your personal account on {% data variables.product.prodname_ghe_server %} from {% data variables.product.prodname_mobile %}, you can sign out of the account. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, swipe left on the account to sign out of, then tap **Sign out**.
|
||||
If you no longer need to access data for your personal account on {% data variables.product.prodname_ghe_server %} from {% data variables.product.prodname_mobile %}, you can sign out of the account. At the bottom of the app, long-press {% octicon "person" aria-hidden="true" %} **Profile**, swipe left on the account to sign out of, then tap **Sign out**.
|
||||
|
||||
## Supported languages for {% data variables.product.prodname_mobile %}
|
||||
|
||||
|
|
|
|||
|
|
@ -31,7 +31,7 @@ This type of permanent link will render as a code snippet only in the repository
|
|||
{% data reusables.repositories.navigate-to-repo %}
|
||||
1. Locate the code you'd like to link to:
|
||||
- To link to code from a file, navigate to the file.
|
||||
- To link to code from a pull request, navigate to the pull request and click {% octicon "diff" aria-label="The file diff icon" %} **Files changed**. Then, browse to the file that contains the code you want include in your comment, and click **View**.
|
||||
- To link to code from a pull request, navigate to the pull request and click {% octicon "diff" aria-hidden="true" %} **Files changed**. Then, browse to the file that contains the code you want include in your comment, and click **View**.
|
||||
{% data reusables.repositories.choose-line-or-range %}
|
||||
1. To the left of the line or range of lines, click {% octicon "kebab-horizontal" aria-label="Code line X options" %}. In the drop-down menu, click **Copy permalink**.
|
||||
|
||||
|
|
|
|||
|
|
@ -18,18 +18,18 @@ Alternatively, you can download the latest version of the public schema here:
|
|||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
[{% octicon "desktop-download" aria-label="The desktop download icon" %} `schema.docs.graphql`](/public/schema.docs.graphql)
|
||||
[{% octicon "desktop-download" aria-label="Download" %} `schema.docs.graphql`](/public/schema.docs.graphql)
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghes %}
|
||||
|
||||
[{% octicon "desktop-download" aria-label="The desktop download icon" %} `schema.docs-enterprise.graphql`](/public/ghes-{{ allVersions[currentVersion].currentRelease }}/schema.docs-enterprise.graphql) ({{ allVersions[currentVersion].versionTitle }})
|
||||
[{% octicon "desktop-download" aria-label="Download" %} `schema.docs-enterprise.graphql`](/public/ghes-{{ allVersions[currentVersion].currentRelease }}/schema.docs-enterprise.graphql) ({{ allVersions[currentVersion].versionTitle }})
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghae %}
|
||||
|
||||
[{% octicon "desktop-download" aria-label="The desktop download icon" %} `schema.docs-ghae.graphql`](/public/ghae/schema.docs-ghae.graphql) ({{ allVersions[currentVersion].versionTitle }})
|
||||
[{% octicon "desktop-download" aria-label="Download" %} `schema.docs-ghae.graphql`](/public/ghae/schema.docs-ghae.graphql) ({{ allVersions[currentVersion].versionTitle }})
|
||||
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -38,7 +38,7 @@ You can also configure workflow automations to keep your {% data variables.proje
|
|||
1. On the top of your profile page, in the main navigation, click {% octicon "project" aria-hidden="true" %} **Projects**.
|
||||
|
||||
{% ifversion projects-v2 %}
|
||||
|
||||
|
||||
1. Click **Projects (classic)**{% endif %}
|
||||
{% data reusables.project-management.click-new-project %}
|
||||
{% data reusables.project-management.create-project-name-description %}
|
||||
|
|
|
|||
|
|
@ -35,7 +35,7 @@ You can put a maximum of 2,500 cards into each project column. If a column has r
|
|||
## Adding issues and pull requests to a {% data variables.projects.projects_v1_board %}
|
||||
|
||||
1. Navigate to the {% data variables.projects.projects_v1_board %} where you want to add issues and pull requests.
|
||||
2. In your {% data variables.projects.projects_v1_board %}, click {% octicon "plus" aria-label="The plus icon" %} **Add cards**.
|
||||
2. In your {% data variables.projects.projects_v1_board %}, click {% octicon "plus" aria-hidden="true" %} **Add cards**.
|
||||
|
||||
3. Search for issues and pull requests to add to your {% data variables.projects.projects_v1_board %} using search qualifiers such as `is:issue is:open`. For more information on search qualifiers you can use, see "[AUTOTITLE](/search-github/searching-on-github/searching-issues-and-pull-requests)."
|
||||
|
||||
|
|
@ -59,7 +59,7 @@ You can put a maximum of 2,500 cards into each project column. If a column has r
|
|||
1. On the right side of an issue or pull request, click **Projects {% octicon "gear" aria-label="The Gear icon" %}**.
|
||||
|
||||
|
||||
|
||||
|
||||
2. Click the **Recent**, **Repository**, **User**, or **Organization** tab for the {% data variables.projects.projects_v1_board %} you would like to add to.
|
||||
3. Type the name of the project in **Filter projects** field.
|
||||
4. Select one or more {% data variables.projects.projects_v1_boards %} where you want to add the issue or pull request.
|
||||
|
|
|
|||
|
|
@ -41,10 +41,10 @@ You can migrate your project boards to the new {% data variables.product.prodnam
|
|||
|
||||
{% data reusables.projects.enable-migration %}
|
||||
1. In the top right corner of {% data variables.product.prodname_dotcom_the_website %}, click your profile photo, then click **Your projects**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. On the top of your profile page, in the main navigation, click {% octicon "table" aria-label="The project board icon" %} **Projects**.
|
||||
|
||||
1. On the top of your profile page, in the main navigation, click {% octicon "table" aria-hidden="true" %} **Projects**.
|
||||
|
||||
1. Above the list of projects, click **Projects (classic)**.
|
||||
{% data reusables.projects.migrate-project-steps %}
|
||||
|
|
@ -59,6 +59,6 @@ You can migrate your project boards to the new {% data variables.product.prodnam
|
|||
|
||||
{% data reusables.projects.enable-migration %}
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
1. Under your repository name, click {% octicon "table" aria-label="The project board icon" %} **Projects**.
|
||||
1. Under your repository name, click {% octicon "table" aria-hidden="true" %} **Projects**.
|
||||
1. In the left sidebar, click **Projects (classic)**.
|
||||
{% data reusables.projects.migrate-project-steps %}
|
||||
|
|
|
|||
|
|
@ -23,7 +23,7 @@ You can set the date or iteration fields that your roadmap will use to position
|
|||
|
||||
|
||||
|
||||
1. Optionally, to create a new date or iteration field, click {% octicon "plus" aria-label="the plus icon" %} **New field**, type the name of your field, and click **Save**. You can then select the new field or create another.
|
||||
1. Optionally, to create a new date or iteration field, click {% octicon "plus" aria-hidden="true" %} **New field**, type the name of your field, and click **Save**. You can then select the new field or create another.
|
||||
1. Select a date or iteration field for "Start date" and "Target date."
|
||||
|
||||
{% ifversion projects-v2-roadmap-markers %}
|
||||
|
|
|
|||
|
|
@ -81,7 +81,7 @@ Specify a priority for all issues in your project.
|
|||
Next, group all of the items in your project by priority to make it easier to focus on the high priority items.
|
||||
|
||||
{% data reusables.projects.open-view-menu %}
|
||||
1. Click {% octicon "rows" aria-label="the rows icon" %} **Group**.
|
||||
1. Click {% octicon "rows" aria-hidden="true" %} **Group**.
|
||||
1. Click **Priority**.
|
||||
|
||||
Now, move issues between groups to change their priority.
|
||||
|
|
@ -121,7 +121,7 @@ When you changed the layout, your project displayed an indicator to show that th
|
|||
To indicate the purpose of the view, give it a descriptive name.
|
||||
|
||||
{% data reusables.projects.open-view-menu %}
|
||||
1. Click {% octicon "pencil" aria-label="the pencil icon" %} **Rename view**.
|
||||
1. Click {% octicon "pencil" aria-hidden="true" %} **Rename view**.
|
||||
1. Type the new name for your view.
|
||||
1. To save changes, press <kbd>Return</kbd>.
|
||||
|
||||
|
|
@ -149,7 +149,7 @@ Finally, add a built in workflow to set the status to **Todo** when an item is a
|
|||
|
||||
1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu.
|
||||
|
||||
1. In the menu, click {% octicon "workflow" aria-label="The workflow icon" %} **Workflows**.
|
||||
1. In the menu, click {% octicon "workflow" aria-hidden="true" %} **Workflows**.
|
||||
1. Under **Default workflows**, click **Item added to project**.
|
||||
1. Next to **When**, ensure that both `issues` and `pull requests` are selected.
|
||||
1. Next to **Set**, select **Status:Todo**.
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ You can list relevant projects in a repository. You can only list projects that
|
|||
In order for repository members to see a project listed in a repository, they must have visibility for the project. For more information, see "[AUTOTITLE](/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects)" and "[AUTOTITLE](/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects)."
|
||||
|
||||
1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of your repository.
|
||||
1. Click {% octicon "table" aria-label="the project icon" %} **Projects**.
|
||||
1. Click {% octicon "table" aria-hidden="true" %} **Projects**.
|
||||
|
||||
1. Click **Add project**.
|
||||
1. In the search bar that appears, search for projects that are owned by the same user or organization that owns the repository.
|
||||
|
|
|
|||
|
|
@ -107,7 +107,7 @@ When you create an issue from a discussion, the contents of the discussion post
|
|||
|
||||
{% data reusables.discussions.discussions-tab %}
|
||||
{% data reusables.discussions.click-discussion-in-list %}
|
||||
1. In the right sidebar, click {% octicon "issue-opened" aria-label="The issues icon" %} **Create issue from discussion**.
|
||||
1. In the right sidebar, click {% octicon "issue-opened" aria-hidden="true" %} **Create issue from discussion**.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -29,7 +29,7 @@ If you are not using {% data variables.product.prodname_ghe_cloud %}, you can fi
|
|||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.compliance %}
|
||||
1. To the right of the report you want to access, click {% octicon "download" aria-label="The Download icon" %} **Download** or {% octicon "link-external" aria-label="The external link icon" %} **View**.
|
||||
1. To the right of the report you want to access, click {% octicon "download" aria-hidden="true" %} **Download** or {% octicon "link-external" aria-hidden="true" %} **View**.
|
||||
|
||||
{% data reusables.security.compliance-report-screenshot %}
|
||||
|
||||
|
|
|
|||
|
|
@ -54,8 +54,9 @@ If a team's access to a {% data variables.projects.projects_v1_board %} is inher
|
|||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.user-settings.access_org %}
|
||||
{% data reusables.organizations.specific_team %}
|
||||
1. Above the team's conversation, click {% octicon "project" aria-label="The Projects icon" %} **Projects**.
|
||||
|
||||
1. Above the team's conversation, click {% octicon "project" aria-hidden="true" %} **Projects**.
|
||||
|
||||
|
||||
1. To change permissions levels, to the right of the {% data variables.projects.projects_v1_board %} you want to update, use the permission level dropdown menu.
|
||||
|
||||
{% ifversion projects-v2-add-to-team %}
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ permissions: 'Organization owners can allow {% data variables.projects.project_v
|
|||
|
||||
## About visibility changes for projects
|
||||
|
||||
You can restrict who has the ability to change the visibility of {% data variables.projects.projects_v2_and_v1 %} in your organization, such as restricting members from changing {% data variables.projects.projects_v2_and_v1 %} from private to public.
|
||||
You can restrict who has the ability to change the visibility of {% data variables.projects.projects_v2_and_v1 %} in your organization, such as restricting members from changing {% data variables.projects.projects_v2_and_v1 %} from private to public.
|
||||
|
||||
You can limit the ability to change {% data variables.projects.project_v2_and_v1 %} visibility to just organization owners, or you can allow anyone granted admin permissions to change the visibility.
|
||||
|
||||
|
|
@ -25,7 +25,7 @@ This option may not be available to you if an enterprise owner restricts visibil
|
|||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "table" aria-label="The table icon" %} Projects**.
|
||||
1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "table" aria-hidden="true" %} Projects**.
|
||||
1. To allow members to adjust project visibility, select **Allow members to change project visibilities for this organization**.
|
||||
1. Click **Save**.
|
||||
|
||||
|
|
|
|||
|
|
@ -178,7 +178,7 @@ For each repository in your organization, you can see how much cache storage a r
|
|||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
1. In the left sidebar, click {% octicon "play" aria-label="The {% data variables.product.prodname_actions %} icon" %} **Actions**, then click **Caches**.
|
||||
1. In the left sidebar, click {% octicon "play" aria-hidden="true" %} **Actions**, then click **Caches**.
|
||||
1. Review the list of repositories for information about their {% data variables.product.prodname_actions %} caches. You can click on a repository name to see more detail about the repository's caches.
|
||||
|
||||
{% ifversion actions-cache-admin-ui %}
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ You can also enable code review limits for individual repositories. If you enabl
|
|||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
1. In the "Access" section of the sidebar, click **{% octicon "report" aria-label="The report icon" %} Moderation**.
|
||||
1. In the "Access" section of the sidebar, click **{% octicon "report" aria-hidden="true" %} Moderation**.
|
||||
1. Under "{% octicon "report" aria-hidden="true" %} Moderation", click **Code review limits**.
|
||||
1. Review the information on screen.
|
||||
1. Manage code review limits.
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ Organization admins can also use the REST API to review and manage {% data varia
|
|||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
1. In the left sidebar, under **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}s**, click **Pending requests**. If any tokens are pending approval for your organization, they will be displayed.
|
||||
1. In the left sidebar, under **{% octicon "key" aria-hidden="true" %} {% data variables.product.pat_generic_caps %}s**, click **Pending requests**. If any tokens are pending approval for your organization, they will be displayed.
|
||||
1. Click the name of the token that you want to approve or deny.
|
||||
1. Review the access and permissions that the token is requesting.
|
||||
1. To grant the token access to the organization, click **Approve**. To deny the token access to the organization, click **Deny**.
|
||||
|
|
@ -40,8 +40,7 @@ Alternatively, you can approve or deny multiple tokens at once:
|
|||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
1. In the left sidebar, under **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}s**, click **Pending requests**. If any tokens are pending approval for your organization, they will be displayed.
|
||||
1. In the left sidebar, under **{% octicon "key" aria-hidden="true" %} {% data variables.product.pat_generic_caps %}s**, click **Pending requests**. If any tokens are pending approval for your organization, they will be displayed.
|
||||
{% data reusables.user-settings.patv2-filters %}
|
||||
1. Select each token that you want to approve or reject.
|
||||
1. Select the **request selected...** dropdown menu and click **Approve...** or **Deny...**.
|
||||
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ Organization owners can only view and revoke {% data variables.product.pat_v2 %}
|
|||
|
||||
{% ifversion ghec %} Organization owners can also view and revoke {% data variables.product.pat_v1_plural %} if their organization requires SAML single-sign on. For more information, see "[AUTOTITLE](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise#viewing-and-revoking-authorized-credentials)". For more information about using the REST API to do this, see "[List SAML SSO authorizations for an organization](/rest/orgs/orgs#list-saml-sso-authorizations-for-an-organization)" and "[Remove a SAML SSO authorization for an organization](/rest/orgs/orgs#remove-a-saml-sso-authorization-for-an-organization)."{% endif %}
|
||||
|
||||
{% ifversion pat-v2-org-admin-api %}
|
||||
{% ifversion pat-v2-org-admin-api %}
|
||||
|
||||
Organization admins can also use the REST API to review and revoke {% data variables.product.pat_v2 %}s. These endpoints can only be called by {% data variables.product.prodname_github_apps %}, and cannot be called with {% data variables.product.pat_generic_plural %} or {% data variables.product.prodname_oauth_apps %}. For more information, see "[AUTOTITLE](/rest/orgs/orgs#list-fine-grained-personal-access-tokens-with-access-to-organization-resources)."
|
||||
|
||||
|
|
@ -28,7 +28,7 @@ Organization admins can also use the REST API to review and revoke {% data varia
|
|||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
1. In the left sidebar, under **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}s**, click **Active tokens**. Any {% data variables.product.pat_v2 %}s that can access your organization will be displayed.
|
||||
1. In the left sidebar, under **{% octicon "key" aria-hidden="true" %} {% data variables.product.pat_generic_caps %}s**, click **Active tokens**. Any {% data variables.product.pat_v2 %}s that can access your organization will be displayed.
|
||||
1. Click the name of the token that you want review or revoke.
|
||||
1. Review the access and permissions that the token has.
|
||||
1. To revoke access by the token to the organization, click **Revoke**.
|
||||
|
|
@ -37,7 +37,7 @@ Alternatively, you can revoke multiple tokens at once:
|
|||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
1. In the left sidebar, under **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}s**, click **Active tokens**. Any {% data variables.product.pat_v2 %}s that can access your organization will be displayed.
|
||||
1. In the left sidebar, under **{% octicon "key" aria-hidden="true" %} {% data variables.product.pat_generic_caps %}s**, click **Active tokens**. Any {% data variables.product.pat_v2 %}s that can access your organization will be displayed.
|
||||
{% data reusables.user-settings.patv2-filters %}
|
||||
1. Select each token that you want to revoke.
|
||||
1. Select the **tokens selected...** dropdown menu and click **Revoke...**.
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ Organization owners can prevent {% data variables.product.pat_v2 %}s from access
|
|||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
1. In the left sidebar, under **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}s**, click **Settings**.
|
||||
1. In the left sidebar, under **{% octicon "key" aria-hidden="true" %} {% data variables.product.pat_generic_caps %}s**, click **Settings**.
|
||||
1. Under **{% data variables.product.pat_v2_caps %}s**, select the option that meets your needs:
|
||||
- **Allow access via {% data variables.product.pat_v2 %}s**: {% data variables.product.pat_v2_caps %}s can access resources owned by the organization.
|
||||
- **Restrict access via {% data variables.product.pat_v2 %}s**: {% data variables.product.pat_v2_caps %}s cannot access resources owned by the organization. SSH keys created by {% data variables.product.pat_v2 %}s will continue to work.
|
||||
|
|
@ -36,7 +36,7 @@ Organization owners can require approval for each {% data variables.product.pat_
|
|||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
1. In the left sidebar, under **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}s**, click **Settings**.
|
||||
1. In the left sidebar, under **{% octicon "key" aria-hidden="true" %} {% data variables.product.pat_generic_caps %}s**, click **Settings**.
|
||||
1. Under **Require approval of {% data variables.product.pat_v2 %}s**, select the option that meets your needs:
|
||||
- **Require administrator approval**: An organization owner must approve each {% data variables.product.pat_v2 %} that can access the organization. {% data variables.product.pat_v2_caps %}s created by organization owners will not need approval.
|
||||
- **Do not require administrator approval**: {% data variables.product.pat_v2_caps %}s created by organization members can access resources in the organization without prior approval.
|
||||
|
|
@ -50,7 +50,7 @@ Organization owners can prevent {% data variables.product.pat_v1_plural %} from
|
|||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
1. In the left sidebar, under **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}s**, click **Settings**.
|
||||
1. In the left sidebar, under **{% octicon "key" aria-hidden="true" %} {% data variables.product.pat_generic_caps %}s**, click **Settings**.
|
||||
1. Under **{% data variables.product.pat_v1_caps %}**, select the option that meets your needs:
|
||||
- **Allow access via {% data variables.product.pat_v1_plural %}**: {% data variables.product.pat_v1_caps_plural %} can access resources owned by the organization.
|
||||
- **Restrict access via {% data variables.product.pat_v1_plural %}**: {% data variables.product.pat_v1_caps_plural %} cannot access resources owned by the organization. SSH keys created by {% data variables.product.pat_v1_plural %} will continue to work.
|
||||
|
|
|
|||
|
|
@ -54,7 +54,7 @@ Any team members that have set their status to "Busy" will not be selected for r
|
|||
{% data reusables.organizations.specific_team %}
|
||||
{% data reusables.organizations.team_settings %}
|
||||
{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
|
||||
1. In the left sidebar, click **{% octicon "code-review" aria-label="The code-review icon" %} Code review**.
|
||||
1. In the left sidebar, click **{% octicon "code-review" aria-hidden="true" %} Code review**.
|
||||
{% else %}
|
||||
1. In the left sidebar, click **Code review**
|
||||
{% endif %}
|
||||
|
|
@ -69,7 +69,7 @@ Any team members that have set their status to "Busy" will not be selected for r
|
|||
{% data reusables.organizations.specific_team %}
|
||||
{% data reusables.organizations.team_settings %}
|
||||
{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
|
||||
1. In the left sidebar, click **{% octicon "code-review" aria-label="The code-review icon" %} Code review**.
|
||||
1. In the left sidebar, click **{% octicon "code-review" aria-hidden="true" %} Code review**.
|
||||
{% else %}
|
||||
1. In the left sidebar, click **Code review**
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -50,7 +50,7 @@ You can find and view a package located in the repositories of an organization y
|
|||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.user-settings.access_org %}
|
||||
3. Under your organization name, click {% octicon "package" aria-label="The package icon" %} **Packages**.
|
||||
3. Under your organization name, click {% octicon "package" aria-hidden="true" %} **Packages**.
|
||||
{% data reusables.package_registry.navigate-to-packages %}
|
||||
|
||||
## Viewing your packages
|
||||
|
|
|
|||
|
|
@ -25,7 +25,7 @@ It's also possible to verify a domain for your organization{% ifversion ghec %}
|
|||
## Verifying a domain for your user site
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "browser" aria-label="The pages icon" %} Pages**.
|
||||
1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "browser" aria-hidden="true" %} Pages**.
|
||||
{% data reusables.pages.settings-verify-domain-setup %}
|
||||
1. Wait for your DNS configuration to change, this may be immediate or take up to 24 hours. You can confirm the change to your DNS configuration by running the `dig` command on the command line. In the command below, replace `USERNAME` with your username and `example.com` with the domain you're verifying. If your DNS configuration has updated, you should see your new TXT record in the output.
|
||||
```
|
||||
|
|
@ -39,7 +39,7 @@ Organization owners can verify custom domains for their organization.
|
|||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "browser" aria-label="The browser icon" %} Pages**.
|
||||
1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "browser" aria-hidden="true" %} Pages**.
|
||||
{% data reusables.pages.settings-verify-domain-setup %}
|
||||
1. Wait for your DNS configuration to change. This may be immediate or take up to 24 hours. You can confirm the change to your DNS configuration by running the `dig` command on the command line. In the command below, replace `ORGANIZATION` with the name of your organization and `example.com` with the domain you're verifying. If your DNS configuration has updated, you should see your new TXT record in the output.
|
||||
```
|
||||
|
|
|
|||
|
|
@ -38,8 +38,9 @@ To use a shorter and more memorable domain for your privately published site, yo
|
|||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% data reusables.pages.sidebar-pages %}
|
||||
3. Under "{% data variables.product.prodname_pages %}", select the **{% data variables.product.prodname_pages %} visibility** dropdown menu, then select a visibility.
|
||||
4. To see your published site, under "{% data variables.product.prodname_pages %}", click **{% octicon "link-external" aria-label="The external link icon" %} Visit site**.
|
||||
|
||||
4. To see your published site, under "{% data variables.product.prodname_pages %}", click **{% octicon "link-external" aria-hidden="true" %} Visit site**.
|
||||
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
|
|
|
|||
|
|
@ -130,7 +130,7 @@ By default, when you create a new repository in your personal account, workflows
|
|||
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-label="The gear icon" %} **Settings**.
|
||||
1. Under your repository name, click {% octicon "gear" aria-hidden="true" %} **Settings**.
|
||||
{% data reusables.repositories.settings-sidebar-actions-general %}
|
||||
1. Under **Access**, choose one of the access settings:
|
||||
|
||||
|
|
@ -151,7 +151,7 @@ You can use the steps below to configure whether actions and reusable workflows
|
|||
### Managing access for a private repository
|
||||
|
||||
1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of the private repository.
|
||||
1. Under your repository name, click {% octicon "gear" aria-label="The gear icon" %} **Settings**.
|
||||
1. Under your repository name, click {% octicon "gear" aria-hidden="true" %} **Settings**.
|
||||
{% data reusables.repositories.settings-sidebar-actions-general %}
|
||||
1. Under **Access**, choose one of the access settings:
|
||||
|
||||
|
|
@ -165,7 +165,7 @@ You can use the steps below to configure whether actions and reusable workflows
|
|||
### Managing access for a private repository in an organization
|
||||
|
||||
1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of the private repository.
|
||||
1. Under your repository name, click {% octicon "gear" aria-label="The gear icon" %} **Settings**.
|
||||
1. Under your repository name, click {% octicon "gear" aria-hidden="true" %} **Settings**.
|
||||
{% data reusables.repositories.settings-sidebar-actions-general %}
|
||||
1. Under **Access**, choose one of the access settings:
|
||||
|
||||
|
|
@ -178,7 +178,7 @@ You can use the steps below to configure whether actions and reusable workflows
|
|||
{% ifversion fpt %}{% else %}
|
||||
|
||||
1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of the private repository.
|
||||
1. Under your repository name, click {% octicon "gear" aria-label="The gear icon" %} **Settings**.
|
||||
1. Under your repository name, click {% octicon "gear" aria-hidden="true" %} **Settings**.
|
||||
{% data reusables.repositories.settings-sidebar-actions-general %}
|
||||
1. Under **Access**, choose one of the access settings:
|
||||
* **Not accessible** - Workflows in other repositories cannot access this repository.
|
||||
|
|
|
|||
|
|
@ -23,8 +23,8 @@ Additionally, you can create custom repository roles to allow other groups of us
|
|||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
1. In the "Code and automation" section of the sidebar, click **{% octicon "tag" aria-label="The tag icon" %} Tags**.
|
||||
1. In the "Code and automation" section of the sidebar, click **{% octicon "tag" aria-hidden="true"%} Tags**.
|
||||
1. Click **New rule**.
|
||||
1. Under "Tag name pattern", type the pattern of the tags you want to protect. In this example, typing "\*" protects all tags.
|
||||
1. Under "Tag name pattern", type the pattern of the tags you want to protect. In this example, typing "\*" protects all tags.
|
||||
|
||||
1. Click **Add rule**.
|
||||
|
|
|
|||
|
|
@ -25,14 +25,14 @@ You can download the source code archives in three ways.
|
|||
|
||||
|
||||
|
||||
1. Click {% octicon "file-zip" aria-label="The ZIP icon" %} **Download ZIP**.
|
||||
1. Click {% octicon "file-zip" aria-hidden="true" %} **Download ZIP**.
|
||||
|
||||
### Downloading source code archives from a release
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.releases %}
|
||||
1. Scroll down to the "Assets" section of the release.
|
||||
1. To download the source code, click {% octicon "file-zip" aria-label="The ZIP icon" %} **Source code (zip)** or {% octicon "file-zip" aria-label="The ZIP icon" %} **Source code (tar.gz)**.
|
||||
1. To download the source code, click {% octicon "file-zip" aria-hidden="true" %} **Source code (zip)** or {% octicon "file-zip" aria-hidden="true" %} **Source code (tar.gz)**.
|
||||
|
||||
### Downloading source code archives from a tag
|
||||
|
||||
|
|
|
|||
|
|
@ -38,7 +38,7 @@ For more information about the search syntax of code search, see "[AUTOTITLE](/s
|
|||
## Creating and managing saved searches
|
||||
|
||||
1. In the top navigation of {% data variables.product.prodname_dotcom_the_website %}, click the search bar and type `saved:`.
|
||||
1. Under the search bar, the "Saved searches" section should now appear. Click {% octicon "plus-circle" aria-label="The plus-circle icon" %} **Create saved search**.
|
||||
1. Under the search bar, the "Saved searches" section should now appear. Click {% octicon "plus-circle" aria-hidden="true" %} **Create saved search**.
|
||||
1. In the pop-up window, fill out the name you want for your query and the query that you want to save. Click **Create saved search**.
|
||||
1. If you click again on the search bar, you can now see your saved search in the "Saved searches" section under the search bar. Clicking on a saved search entry will add the query to the search bar and filter the suggestions accordingly.
|
||||
- To edit a saved search, in the "Saved searches" section, click {% octicon "pencil" aria-label="The pencil icon" %} to the right of the saved search.
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ shortTitle: Attribute sponsorships
|
|||
---
|
||||
|
||||
1. Navigate to the organization whose sponsorships you want to attribute to another organization.
|
||||
1. Under your organization name, click {% octicon "heart" aria-label="The heart icon" %} **Sponsoring**.
|
||||
1. Under your organization name, click {% octicon "heart" aria-hidden="true" %} **Sponsoring**.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -8,5 +8,5 @@
|
|||
* **If using an enterprise account**: Navigate to your enterprise account by clicking your profile photo in the top-right corner of {% data variables.product.prodname_dotcom_the_website %}, then clicking **Your enterprises**, then clicking the enterprise.
|
||||
1. Navigate to the {% data variables.product.prodname_actions %} settings:
|
||||
* **In an organization or repository**: Click **Actions** in the left sidebar, then click **Runners**.
|
||||
* **If using an enterprise account**: In the left sidebar, click **"{% octicon "law" aria-label="The law icon" %} Policies"**, then click **Actions**, then click the **Runners** tab.
|
||||
* **If using an enterprise account**: In the left sidebar, click **"{% octicon "law" aria-hidden="true" %} Policies"**, then click **Actions**, then click the **Runners** tab.
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
{% comment %}This reusable is only to be used in other repo/org/enterprise setting reusables.{%- endcomment -%}
|
||||
1. In the left sidebar, click {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}{% octicon "play" aria-label="The {% data variables.product.prodname_actions %} icon" %} **Actions**, then click **Runner groups**.{% else %}**Actions**.{% ifversion ghes or ghae %}
|
||||
1. In the left sidebar, click {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}{% octicon "play" aria-hidden="true" %} **Actions**, then click **Runner groups**.{% else %}**Actions**.{% ifversion ghes or ghae %}
|
||||
1. In the left sidebar, under "Actions", click **Runner groups**.
|
||||
{%- elsif ghes or ghae %}
|
||||
1. In the left sidebar, under "Actions", click **Runners**.{% endif %}{% endif %}
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
{% comment %}This reusable is only to be used in other repo/org/enterprise setting reusables.{%- endcomment -%}
|
||||
1. In the left sidebar, click {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}{% octicon "play" aria-label="The {% data variables.product.prodname_actions %} icon" %} **Actions**, then click **Runners**.{% else %}**Actions**.{% ifversion ghes or ghae %}
|
||||
1. In the left sidebar, click {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}{% octicon "play" aria-hidden="true" %} **Actions**, then click **Runners**.{% else %}**Actions**.{% ifversion ghes or ghae %}
|
||||
1. In the left sidebar, under "Actions", click **Runners**.{% endif %}{% endif %}
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 -%}
|
||||
1. In the "Security" section of the sidebar, select {% ifversion actions-configuration-variables %}**{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets and variables**, {% else %}**{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets**, {% endif %}then click **Actions**.
|
||||
1. In the "Security" section of the sidebar, select {% ifversion actions-configuration-variables %}**{% octicon "key-asterisk" aria-hidden="true" %} Secrets and variables**, {% else %}**{% octicon "key-asterisk" aaria-hidden="true" %} Secrets**, {% endif %}then click **Actions**.
|
||||
{%- else %}
|
||||
1. In the left sidebar, click **Secrets**.
|
||||
{%- endif %}
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
1. Sign into {% data variables.product.prodname_classroom_with_url %}.
|
||||
1. Navigate to a classroom.
|
||||
1. In the {% octicon "repo" aria-label="The repo icon" %} **Assignments** tab, create the assignment.
|
||||
1. In the {% octicon "repo" aria-hidden="true" %} **Assignments** tab, create the assignment.
|
||||
- If this your first assignment, click **Create an assignment**.
|
||||
- Otherwise, click **New assignment** on the right side.
|
||||
|
|
@ -1,3 +1,3 @@
|
|||
1. Under the classroom name, click {% octicon "gear" aria-label="The gear icon" %} **Settings**.
|
||||
1. Under the classroom name, click {% octicon "gear" aria-hidden="true" %} **Settings**.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
1. Under the classroom name, click {% octicon "people" aria-label="The people icon" %} **Students**.
|
||||
1. Under the classroom name, click {% octicon "people" aria-hidden="true" %} **Students**.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
1. In the "Code, planning, and automation" section of the sidebar, select **{% octicon "codespaces" aria-label="The codespaces icon" %} {% data variables.product.prodname_codespaces %}** then click **Policies**.
|
||||
1. In the "Code, planning, and automation" section of the sidebar, select **{% octicon "codespaces" aria-hidden="true" %} {% data variables.product.prodname_codespaces %}** then click **Policies**.
|
||||
1. On the "Codespace policies" page, click **Create Policy**.
|
||||
1. Enter a name for your new policy.
|
||||
|
|
|
|||
|
|
@ -5,4 +5,4 @@
|
|||
|
||||
|
||||
|
||||
Alternatively, you can see any of your codespaces for a specific repository by navigating to that repository and selecting **{% octicon "code" aria-label="The code icon" %} Code**. The dropdown menu will display all active codespaces for a repository.
|
||||
Alternatively, you can see any of your codespaces for a specific repository by navigating to that repository and selecting **{% octicon "code" aria-hidden="true" %} Code**. The dropdown menu will display all active codespaces for a repository.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
1. In the "Security" section of the sidebar, select {% ifversion actions-configuration-variables %}**{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets and variables**, {% else %}**{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets**, {% endif %}then click **{% data variables.product.prodname_codespaces %}**.
|
||||
1. In the "Security" section of the sidebar, select {% ifversion actions-configuration-variables %}**{% octicon "key-asterisk" aria-hidden="true" %} Secrets and variables**, {% else %}**{% octicon "key-asterisk" aria-hidden="true" %} Secrets**, {% endif %}then click **{% data variables.product.prodname_codespaces %}**.
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "copilot" aria-label="The copilot icon" %} {% data variables.product.prodname_copilot_short %}**, and then click **Access**.
|
||||
1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "copilot" aria-hidden="true" %} {% data variables.product.prodname_copilot_short %}**, and then click **Access**.
|
||||
1. Under "User permissions," to disable {% data variables.product.prodname_copilot %} for all users in your organization, select **Disabled**.
|
||||
1. To save your changes, click **Save**.
|
||||
|
|
@ -1,5 +1,5 @@
|
|||
{% data reusables.user-settings.access_settings %}
|
||||
1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "copilot" aria-label="The copilot icon" %} {% data variables.product.prodname_copilot %}**.
|
||||
1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "copilot" aria-hidden="true" %} {% data variables.product.prodname_copilot %}**.
|
||||
1. On the {% data variables.product.prodname_copilot %} settings page, click **Enable {% data variables.product.prodname_copilot %}**.
|
||||
1. Choose whether you want to pay monthly or yearly, and click **Continue to get access to Copilot**.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
|
||||
1. In the "Security" section of the sidebar, select {% ifversion actions-configuration-variables %}**{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets and variables**, {% else %}**{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets**, {% endif %}then click **{% data variables.product.prodname_dependabot %}**.
|
||||
1. In the "Security" section of the sidebar, select {% ifversion actions-configuration-variables %}**{% octicon "key-asterisk" aria-hidden="true" %} Secrets and variables**, {% else %}**{% octicon "key-asterisk" aria-hidden="true"%} Secrets**, {% endif %}then click **{% data variables.product.prodname_dependabot %}**.
|
||||
{% else %}
|
||||
1. In the sidebar, click **{% data variables.product.prodname_dependabot %}**.
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
1. At the top of the app, click {% octicon "git-branch" aria-label="The branch icon" %} **Current Branch** and then in the list of branches, click the branch that you want to base your new branch on.
|
||||
1. At the top of the app, click {% octicon "git-branch" aria-hidden="true" %} **Current Branch** and then in the list of branches, click the branch that you want to base your new branch on.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
1. In {% data variables.product.prodname_desktop %}, click {% octicon "git-branch" aria-label="The branch icon" %} **Current Branch**.
|
||||
1. In {% data variables.product.prodname_desktop %}, click {% octicon "git-branch" aria-hidden="true" %} **Current Branch**.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
1. If you are not already on the branch where the changes are stashed, in the repository bar, click {% octicon "git-branch" aria-label="The branch icon" %} **Current Branch**, then click the branch with stashed changes.
|
||||
1. If you are not already on the branch where the changes are stashed, in the repository bar, click {% octicon "git-branch" aria-hidden="true" %} **Current Branch**, then click the branch with stashed changes.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
1. In the repository bar, click {% octicon "git-branch" aria-label="The branch icon" %} **Current Branch**, then click the branch that you want to delete.
|
||||
1. In the repository bar, click {% octicon "git-branch" aria-hidden="true" %} **Current Branch**, then click the branch that you want to delete.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
1. Under your repository or organization name, click {% octicon "comment-discussion" aria-label="The discussion icon" %} **Discussions**.
|
||||
1. Under your repository or organization name, click {% octicon "comment-discussion" aria-hidden="true" %} **Discussions**.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@
|
|||
|
||||
1. Under "Poll question", type a question for your poll.
|
||||
1. Under "Poll options", type at least two options for your poll.
|
||||
1. Optionally, to add an extra poll option, click **{% octicon "plus" aria-label="The plus icon" %} Add an option**.
|
||||
1. Optionally, to add an extra poll option, click **{% octicon "plus" aria-hidden="true" %} Add an option**.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
1. Under "{% octicon "law" aria-label="The law icon" %} Policies", click **Actions**.
|
||||
1. Under "{% octicon "law" aria-hidden="true" %} Policies", click **Actions**.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
1. Under "{% octicon "law" aria-label="The law icon" %} Policies", click **{% data variables.product.prodname_copilot_short %}**.
|
||||
1. Under "{% octicon "law" aaria-hidden="true" %} Policies", click **{% data variables.product.prodname_copilot_short %}**.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
1. Under {% ifversion ghes or ghae %} {% octicon "law" aria-label="The law icon" %} **Policies**{% else %}"{% octicon "gear" aria-label="The Settings gear" %} Settings"{% endif %}, click **Options**.
|
||||
1. Under {% ifversion ghes or ghae %} {% octicon "law" aria-hidden="true" %} **Policies**{% else %}"{% octicon "gear" aria-hidden="true" %} Settings"{% endif %}, click **Options**.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
1. Under "{% octicon "law" aria-label="The law icon" %} Policies", click **Pages**.
|
||||
1. Under "{% octicon "law" aria-hidden="true" %} Policies", click **Pages**.
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
{% data reusables.user-settings.access_settings %}
|
||||
1. In the "Access" section of the sidebar, click **{% octicon "organization" aria-label="The organization icon" %} Organizations**.
|
||||
1. In the "Access" section of the sidebar, click **{% octicon "organization" aria-hidden="true" %} Organizations**.
|
||||
{% data reusables.profile.org_settings %}
|
||||
1. If you are an organization owner, in the "Access" section of the sidebar, click **{% octicon "credit-card" aria-label="The credit-card icon" %} Billing and plans**.
|
||||
1. If you are an organization owner, in the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing and plans**.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-label="The credit card icon" %} Billing and plans**.
|
||||
1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing and plans**.
|
||||
|
|
@ -1 +1 @@
|
|||
1. In the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation**, then click **Blocked users**.
|
||||
1. In the sidebar, select **{% octicon "report" aria-hidden="true"%} Moderation**, then click **Blocked users**.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
1. In the left sidebar, click **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces**.
|
||||
1. In the left sidebar, click **{% octicon "codespaces" aria-hidden="true" %} Codespaces**.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
1. In the "Security" section of the sidebar, click **{% octicon "checklist" aria-label="The checklist icon" %} Compliance**.
|
||||
1. In the "Security" section of the sidebar, click **{% octicon "checklist" aria-hidden="true" %} Compliance**.
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
|
||||
1. In the left sidebar, select **{% octicon "code" aria-label="The code icon" %} Developer settings** then click **{% data variables.product.prodname_github_apps %}**.
|
||||
1. In the left sidebar, select **{% octicon "code" aria-hidden="true" %} Developer settings** then click **{% data variables.product.prodname_github_apps %}**.
|
||||
{% else %}
|
||||
1. In the left sidebar, click **{% data variables.product.prodname_github_apps %}**.
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
If a person has been given conflicting access, you'll see a warning on the repository access page. The warning appears with "{% octicon "alert" aria-label="The alert icon" %} Mixed roles" next to the person with the conflicting access. To see the source of the conflicting access, hover over the warning icon or click **Mixed roles**.
|
||||
If a person has been given conflicting access, you'll see a warning on the repository access page. The warning appears with "{% octicon "alert" aria-hidden="true" %} Mixed roles" next to the person with the conflicting access. To see the source of the conflicting access, hover over the warning icon or click **Mixed roles**.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
1. In the "Access" section of the sidebar, click **{% octicon "id-badge" aria-label="The ID badge icon" %} Repository roles**.
|
||||
1. In the "Access" section of the sidebar, click **{% octicon "id-badge" aria-hidden="true" %} Repository roles**.
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
|
||||
1. In the "Access" section of the sidebar, click **{% octicon "comment-discussion" aria-label="The comment-discussion icon" %} Team discussions**.
|
||||
1. In the "Access" section of the sidebar, click **{% octicon "comment-discussion" aria-hidden="true" %} Team discussions**.
|
||||
{% else %}
|
||||
1. In the Settings sidebar, click **Teams**.
|
||||
{% endif %}
|
||||
|
|
|
|||
Некоторые файлы не были показаны из-за слишком большого количества измененных файлов Показать больше
Загрузка…
Ссылка в новой задаче