зеркало из https://github.com/github/docs.git
remove single trailing newline
This commit is contained in:
Rachael Sewell
Родитель
05703f4712
Коммит
a785c2be0f
|
|
@ -149,4 +149,4 @@ You can find many examples of composite actions on {% data variables.product.pro
|
|||
|
||||
- [microsoft/action-python](https://github.com/microsoft/action-python)
|
||||
- [microsoft/gpt-review](https://github.com/microsoft/gpt-review)
|
||||
- [tailscale/github-action](https://github.com/tailscale/github-action)
|
||||
- [tailscale/github-action](https://github.com/tailscale/github-action)
|
||||
|
|
|
|||
|
|
@ -291,4 +291,4 @@ jobs:
|
|||
You can find many examples of JavaScript actions on {% data variables.product.prodname_dotcom_the_website %}.
|
||||
|
||||
- [DevExpress/testcafe-action](https://github.com/DevExpress/testcafe-action)
|
||||
- [duckduckgo/privacy-configuration](https://github.com/duckduckgo/privacy-configuration)
|
||||
- [duckduckgo/privacy-configuration](https://github.com/duckduckgo/privacy-configuration)
|
||||
|
|
|
|||
|
|
@ -84,4 +84,4 @@ Once a workflow reaches a job that references an environment that has the custom
|
|||
|
||||
You can publish your {% data variables.product.prodname_github_app %} to the {% data variables.product.prodname_marketplace %} to allow developers to discover suitable protection rules and install it across their {% data variables.product.company_short %} repositories. Or you can browse existing custom deployment protection rules to suit your needs. For more information, see "[AUTOTITLE](/apps/publishing-apps-to-github-marketplace/github-marketplace-overview/about-github-marketplace)" and "[AUTOTITLE](/apps/publishing-apps-to-github-marketplace/listing-an-app-on-github-marketplace)."
|
||||
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -55,4 +55,4 @@ To use {% data variables.product.company_short %}-hosted runners with Azure VNET
|
|||
|
||||
For more information about configuring Azure, see "[AUTOTITLE](/actions/using-github-hosted-runners/connecting-to-a-private-network/configuring-an-azure-virtual-network-for-your-enterprise)."
|
||||
|
||||
For more information about configuring your {% data variables.product.company_short %} settings to use {% data variables.product.company_short %}-hosted runners with a VNET, see "[AUTOTITLE](/actions/using-github-hosted-runners/connecting-to-a-private-network/configuring-your-github-settings-for-use-with-azure-virtual-network)."
|
||||
For more information about configuring your {% data variables.product.company_short %} settings to use {% data variables.product.company_short %}-hosted runners with a VNET, see "[AUTOTITLE](/actions/using-github-hosted-runners/connecting-to-a-private-network/configuring-your-github-settings-for-use-with-azure-virtual-network)."
|
||||
|
|
|
|||
|
|
@ -37,4 +37,4 @@ You can specify `permissions` at the top level of a workflow, so that the settin
|
|||
|
||||
### Example: Setting the `GITHUB_TOKEN` permissions for one job in a workflow
|
||||
|
||||
{% data reusables.actions.jobs.setting-permissions-specific-jobs-example %}
|
||||
{% data reusables.actions.jobs.setting-permissions-specific-jobs-example %}
|
||||
|
|
|
|||
|
|
@ -65,4 +65,4 @@ Your instance validates the hostnames for proxy exclusion using the list of IANA
|
|||
ghe-config noproxy.exception-tld-list "COMMA-SEPARATED-TLD-LIST"
|
||||
```
|
||||
|
||||
{% data reusables.enterprise.apply-configuration %}
|
||||
{% data reusables.enterprise.apply-configuration %}
|
||||
|
|
|
|||
|
|
@ -65,4 +65,4 @@ Although {% data variables.product.prodname_emus %} is free, the migration proce
|
|||
|
||||
## Further reading
|
||||
|
||||
- "[AUTOTITLE](/admin/identity-and-access-management/using-saml-for-enterprise-iam/deciding-whether-to-configure-saml-for-your-enterprise-or-your-organizations)"
|
||||
- "[AUTOTITLE](/admin/identity-and-access-management/using-saml-for-enterprise-iam/deciding-whether-to-configure-saml-for-your-enterprise-or-your-organizations)"
|
||||
|
|
|
|||
|
|
@ -40,4 +40,4 @@ If you want to migrate to a new identity provider (IdP) or tenant rather than di
|
|||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.security-tab %}
|
||||
1. Under "SAML single sign-on", deselect **Require SAML authentication** or **Require OIDC single sign-on**.
|
||||
1. Click **Save**.
|
||||
1. Click **Save**.
|
||||
|
|
|
|||
|
|
@ -25,4 +25,4 @@ If you need to protect internal repositories or enforce a consistent authenticat
|
|||
|
||||
SCIM is not available for enterprise accounts, and team synchronization is only available for SAML at the enterprise level if you use Azure AD as an IdP. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/using-saml-for-enterprise-iam/managing-team-synchronization-for-organizations-in-your-enterprise)."
|
||||
|
||||
Regardless of the SAML implementation you choose, you cannot add external collaborators to organizations or teams. You can only add external collaborators to individual repositories.
|
||||
Regardless of the SAML implementation you choose, you cannot add external collaborators to organizations or teams. You can only add external collaborators to individual repositories.
|
||||
|
|
|
|||
|
|
@ -36,4 +36,4 @@ If you enable the collection of data about {% data variables.product.prodname_ac
|
|||
```shell{:copy}
|
||||
ghe-config app.github.enable-actions-usage-stats true
|
||||
```
|
||||
{% data reusables.enterprise.apply-configuration %}
|
||||
{% data reusables.enterprise.apply-configuration %}
|
||||
|
|
|
|||
|
|
@ -38,4 +38,4 @@ If you're an organization owner, you can enable {% data variables.product.prodna
|
|||
|
||||
You can enable for all organizations, enable for specific organizations, or disable for all organizations.
|
||||
1. Click **Save**.
|
||||
1. Read the confirmation dialog, then click **Submit** to proceed.
|
||||
1. Read the confirmation dialog, then click **Submit** to proceed.
|
||||
|
|
|
|||
|
|
@ -71,4 +71,4 @@ Enterprise owners can choose whether to grant access to {% data variables.produc
|
|||
## Further reading
|
||||
|
||||
- "[AUTOTITLE](/free-pro-team@latest/site-policy/privacy-policies/github-copilot-for-business-privacy-statement)"
|
||||
- [{% data variables.product.prodname_copilot %} Trust Center](https://resources.github.com/copilot-trust-center/)
|
||||
- [{% data variables.product.prodname_copilot %} Trust Center](https://resources.github.com/copilot-trust-center/)
|
||||
|
|
|
|||
|
|
@ -1611,4 +1611,4 @@ If you want to share your app with other users and organizations, make your app
|
|||
|
||||
### Follow best practices
|
||||
|
||||
You should aim to follow best practices with your {% data variables.product.prodname_github_app %}. For more information, see "[AUTOTITLE](/apps/creating-github-apps/setting-up-a-github-app/best-practices-for-creating-a-github-app)."
|
||||
You should aim to follow best practices with your {% data variables.product.prodname_github_app %}. For more information, see "[AUTOTITLE](/apps/creating-github-apps/setting-up-a-github-app/best-practices-for-creating-a-github-app)."
|
||||
|
|
|
|||
|
|
@ -67,4 +67,4 @@ When you cancel a free trial on a paid plan, your subscription is immediately ca
|
|||
{% data reusables.enterprise-accounts.billing-tab %}
|
||||
1. In the "Marketplace apps" tab, find the app you want to cancel.
|
||||
1. Next to the organization where you want to cancel the app, select **{% octicon "kebab-horizontal" aria-label="More" %}** and then click **Cancel plan**.
|
||||
1. Click **Confirm**.
|
||||
1. Click **Confirm**.
|
||||
|
|
|
|||
|
|
@ -142,4 +142,4 @@ If the user account you used to sign into Azure does not have adequate permissio
|
|||
>
|
||||
> GitHub Inc needs permission to access resources in your organisation that only an admin can grant. Please ask an admin to grant permission to this app before you can use it.
|
||||
|
||||
To avoid this message when you try again, you must either ensure that the Azure user can provide tenant-wide admin consent, or you must work with an Azure administrator to configure the admin consent workflow. For more information, review "[Prerequisites](#prerequisites)".
|
||||
To avoid this message when you try again, you must either ensure that the Azure user can provide tenant-wide admin consent, or you must work with an Azure administrator to configure the admin consent workflow. For more information, review "[Prerequisites](#prerequisites)".
|
||||
|
|
|
|||
|
|
@ -129,4 +129,4 @@ You can select all of the displayed repositories, or a subset of them, and enabl
|
|||
|
||||
If you're blocked from enabling {% data variables.product.prodname_code_scanning %} due to an enterprise policy, you will still be able to see the affected repository in the "Security Coverage" view and access the side panel from the **{% octicon "gear" aria-hidden="true" %} Security settings** button. However, you will see a message in the side panel indicating that you cannot enable {% data variables.product.prodname_code_scanning %} for the selected repositories. For more information about enterprise policies, see "[AUTOTITLE](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-code-security-and-analysis-for-your-enterprise)."
|
||||
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -60,4 +60,4 @@ For default setup, you need to define the models of your additional dependencies
|
|||
|
||||
To use {% data variables.product.prodname_codeql %} model packs with default setup, place them in the `.github/codeql/extensions` directory. They will be automatically detected and used in your {% data variables.product.prodname_code_scanning %} analysis. If you later change your configuration to use advanced setup, any data extensions in the `.github/codeql/extensions` directory will still be recognized and used.
|
||||
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -15,4 +15,4 @@ To enable default setup when a language previously failed, you must reconfigure
|
|||
1. In the "Jobs" section of the workflow run summary for default setup, identify any failing jobs associated with specific languages. These jobs will be labeled {% octicon "x-circle-fill" aria-label="failed" %} **Analyze (LANGUAGE)**.
|
||||
1. Once you have determined which language-specific jobs are failing, configure default setup once more and deselect the failing languages for analysis. For more information, see "[AUTOTITLE](/code-security/code-scanning/enabling-code-scanning/configuring-default-setup-for-code-scanning)."
|
||||
|
||||
Alternatively, if you would like to analyze every language in your repository, you can configure advanced setup for {% data variables.product.prodname_code_scanning %}. For more information, see "[AUTOTITLE](/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/configuring-advanced-setup-for-code-scanning)."
|
||||
Alternatively, if you would like to analyze every language in your repository, you can configure advanced setup for {% data variables.product.prodname_code_scanning %}. For more information, see "[AUTOTITLE](/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/configuring-advanced-setup-for-code-scanning)."
|
||||
|
|
|
|||
|
|
@ -12,4 +12,4 @@ versions:
|
|||
|
||||
{% data reusables.code-scanning.beta %}
|
||||
{% data reusables.code-scanning.codeql-action-version-ghes %}
|
||||
{% data reusables.code-scanning.alerts-found-in-generated-code %}
|
||||
{% data reusables.code-scanning.alerts-found-in-generated-code %}
|
||||
|
|
|
|||
|
|
@ -13,4 +13,4 @@ versions:
|
|||
{% data reusables.code-scanning.beta %}
|
||||
{% data reusables.code-scanning.codeql-action-version-ghes %}
|
||||
|
||||
If an automatic build of code for a compiled language within your project fails, you can try removing the `autobuild` step from your {% data variables.product.prodname_code_scanning %} workflow and adding specific build steps. If you're not already using advanced setup, you'll need to enable it first to create a workflow you can edit. For more information about advanced setup, see "[AUTOTITLE](/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning)." For more information about specifically replacing the `autobuild` step, see "[AUTOTITLE](/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/codeql-code-scanning-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
|
||||
If an automatic build of code for a compiled language within your project fails, you can try removing the `autobuild` step from your {% data variables.product.prodname_code_scanning %} workflow and adding specific build steps. If you're not already using advanced setup, you'll need to enable it first to create a workflow you can edit. For more information about advanced setup, see "[AUTOTITLE](/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning)." For more information about specifically replacing the `autobuild` step, see "[AUTOTITLE](/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/codeql-code-scanning-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
|
||||
|
|
|
|||
|
|
@ -12,4 +12,4 @@ When you enable default setup, a workflow is triggered with the automatically ge
|
|||
|
||||
You can check on the progress of the test run for default setup on the **Actions** tab. If the run is taking too long, try canceling the workflow run and restarting the configuration process.
|
||||
|
||||
To restart your configuration, 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="cancelled" %} appears beside the workflow run name, navigate back to the **Code security and analysis** settings and re-enable default setup. If default setup continues to stall, please contact {% data variables.contact.contact_support %} or try enabling advanced setup. For more information, see "[AUTOTITLE](/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/configuring-advanced-setup-for-code-scanning)."
|
||||
To restart your configuration, 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="cancelled" %} appears beside the workflow run name, navigate back to the **Code security and analysis** settings and re-enable default setup. If default setup continues to stall, please contact {% data variables.contact.contact_support %} or try enabling advanced setup. For more information, see "[AUTOTITLE](/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/configuring-advanced-setup-for-code-scanning)."
|
||||
|
|
|
|||
|
|
@ -15,4 +15,4 @@ versions:
|
|||
The {% data variables.product.prodname_codeql %} team constantly works on critical extraction errors to make sure that all source files can be scanned. However, the {% data variables.product.prodname_codeql %} extractors do occasionally generate errors during database creation. {% data variables.product.prodname_codeql %} provides information about extraction errors and warnings generated during database creation in a log file.
|
||||
The extraction diagnostics information gives an indication of overall database health. Most extractor errors do not significantly impact the analysis. A small number of extractor errors is healthy and typically indicates a good state of analysis.
|
||||
|
||||
However, if you see extractor errors in the overwhelming majority of files that were compiled during database creation, you should look into the errors in more detail to try to understand why some source files weren't extracted properly.
|
||||
However, if you see extractor errors in the overwhelming majority of files that were compiled during database creation, you should look into the errors in more detail to try to understand why some source files weren't extracted properly.
|
||||
|
|
|
|||
|
|
@ -44,4 +44,4 @@ You can create {% data variables.product.prodname_codeql %} debugging artifacts
|
|||
uses: {% data reusables.actions.action-codeql-action-init %}
|
||||
with:
|
||||
debug: true
|
||||
```
|
||||
```
|
||||
|
|
|
|||
|
|
@ -45,4 +45,4 @@ If your workflow fails with `Error: "No source code was seen during the build"`
|
|||
|
||||
If you encounter another problem with your specific compiler or configuration, contact {% data variables.contact.contact_support %}.
|
||||
|
||||
For more information about specifying build steps, see "[AUTOTITLE](/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/codeql-code-scanning-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
|
||||
For more information about specifying build steps, see "[AUTOTITLE](/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/codeql-code-scanning-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
|
||||
|
|
|
|||
|
|
@ -25,4 +25,4 @@ Self-hosted runners offer more control of hardware, operating system, and softwa
|
|||
{% ifversion actions-hosted-runners %}
|
||||
## Use larger runners
|
||||
You can use larger runners, which are {% data variables.product.company_short %}-hosted runners with more RAM, CPU, and disk space than standard runners. These runners have the runner application and other tools preinstalled. For more information about larger runners and the specifications you can use with them, see "[AUTOTITLE](/actions/using-github-hosted-runners/about-larger-runners)."{% endif %}
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -43,4 +43,4 @@ If the {% data variables.code-scanning.codeql_workflow %} still fails on a commi
|
|||
- whether {% data variables.product.prodname_dependabot %} authored the commit
|
||||
- whether the pull request that includes the commit has been merged using `@dependabot squash and merge`
|
||||
|
||||
This type of merge commit is authored by {% data variables.product.prodname_dependabot %} and therefore, any workflows running on the commit will have read-only permissions. If you enabled {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_dependabot %} security updates or version updates on your repository, we recommend you avoid using the {% data variables.product.prodname_dependabot %} `@dependabot squash and merge` command. Instead, you can enable auto-merge for your repository. This means that pull requests will be automatically merged when all required reviews are met and status checks have passed. For more information about enabling auto-merge, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request#enabling-auto-merge)."
|
||||
This type of merge commit is authored by {% data variables.product.prodname_dependabot %} and therefore, any workflows running on the commit will have read-only permissions. If you enabled {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_dependabot %} security updates or version updates on your repository, we recommend you avoid using the {% data variables.product.prodname_dependabot %} `@dependabot squash and merge` command. Instead, you can enable auto-merge for your repository. This means that pull requests will be automatically merged when all required reviews are met and status checks have passed. For more information about enabling auto-merge, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request#enabling-auto-merge)."
|
||||
|
|
|
|||
|
|
@ -10,4 +10,4 @@ versions:
|
|||
|
||||
{% data reusables.code-scanning.beta %}
|
||||
|
||||
If the run of a workflow for {% data variables.product.prodname_code_scanning %} fails due to a server error, try running the workflow again. If the problem persists, contact {% data variables.contact.contact_support %}.
|
||||
If the run of a workflow for {% data variables.product.prodname_code_scanning %} fails due to a server error, try running the workflow again. If the problem persists, contact {% data variables.contact.contact_support %}.
|
||||
|
|
|
|||
|
|
@ -37,4 +37,4 @@ If you're using advanced setup and your workflow doesn't explicitly specify the
|
|||
languages: {% raw %}${{ matrix.language }}{% endraw %}
|
||||
```
|
||||
|
||||
For more information about editing the workflow, see "[AUTOTITLE](/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/customizing-your-advanced-setup-for-code-scanning)."
|
||||
For more information about editing the workflow, see "[AUTOTITLE](/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/customizing-your-advanced-setup-for-code-scanning)."
|
||||
|
|
|
|||
|
|
@ -13,4 +13,4 @@ Default setup overrides existing {% data variables.product.prodname_codeql %} se
|
|||
|
||||
Optionally, if you are certain you no longer need the pre-existing workflow file, you can delete the file from your repository. For more information, see "[AUTOTITLE](/repositories/working-with-files/managing-files/deleting-files-in-a-repository)."
|
||||
|
||||
{% data reusables.code-scanning.troubleshooting-multiple-configurations %}
|
||||
{% data reusables.code-scanning.troubleshooting-multiple-configurations %}
|
||||
|
|
|
|||
|
|
@ -11,4 +11,4 @@ versions:
|
|||
|
||||
The {% data variables.code-scanning.tool_status_page %} shows you how well {% data variables.product.prodname_code_scanning %} tools are working for a repository, when files in the repository were first scanned and most recently scanned, and when scans are scheduled. For integrated tools like {% data variables.product.prodname_codeql %}, you can also see more detailed information, including a percentage of files scanned and specific error messages. For more information about the {% data variables.code-scanning.tool_status_page %}, see "[AUTOTITLE](/code-security/code-scanning/managing-your-code-scanning-configuration/about-the-tool-status-page)."
|
||||
|
||||
You can also view the logging output from {% data variables.product.prodname_code_scanning %} runs using {% data variables.product.prodname_actions %} ({% data variables.product.prodname_codeql %} or third-party). For more information, see "[AUTOTITLE](/code-security/code-scanning/managing-your-code-scanning-configuration/viewing-code-scanning-logs#viewing-the-logging-output-from-code-scanning)."
|
||||
You can also view the logging output from {% data variables.product.prodname_code_scanning %} runs using {% data variables.product.prodname_actions %} ({% data variables.product.prodname_codeql %} or third-party). For more information, see "[AUTOTITLE](/code-security/code-scanning/managing-your-code-scanning-configuration/viewing-code-scanning-logs#viewing-the-logging-output-from-code-scanning)."
|
||||
|
|
|
|||
|
|
@ -103,4 +103,4 @@ If there are many deep code paths highlighted in the SARIF results, you can redu
|
|||
|
||||
## Further reading
|
||||
|
||||
- "[AUTOTITLE](/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning)"
|
||||
- "[AUTOTITLE](/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning)"
|
||||
|
|
|
|||
|
|
@ -199,4 +199,4 @@ When a pack is published for use in analyses, the `codeql pack create` or `codeq
|
|||
- For query packs, precompiled representations of each of the queries. These are faster to execute than it would be to compile the QL source for the query at each analysis.
|
||||
|
||||
Most of this data is located in a directory named `.codeql` in the published pack, but precompiled queries are in files with a `.qlx` suffix next to the `.ql` source for each query. When analyzing a database with a query from a published pack, {% data variables.product.prodname_codeql %} will load these files instead of the `.ql` source. If you need to modify the content of a _published_ pack, be sure to remove all of the `.qlx` files, since they may prevent modifications in the `.ql` files from taking effect.
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -109,4 +109,4 @@ codeql github upload-results \
|
|||
```
|
||||
|
||||
This is the same as the process for uploading SARIF files from successful analyses.
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -146,4 +146,4 @@ If no source repository is available and you need to base modifications on a pac
|
|||
|
||||
- Remove all files named `*.qlx` anywhere in the unpacked directory structure. These files contain precompiled versions of the queries, and in some situations {% data variables.product.prodname_codeql %} will use them in preference to the QL source you have modified.
|
||||
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -112,4 +112,4 @@ counter notice form and alert GitHub Support. For more information, see [DMCA co
|
|||
## Next steps
|
||||
|
||||
- "[AUTOTITLE](/code-security/supply-chain-security/end-to-end-supply-chain/securing-code)"
|
||||
- "[AUTOTITLE](/code-security/supply-chain-security/end-to-end-supply-chain/securing-builds)"
|
||||
- "[AUTOTITLE](/code-security/supply-chain-security/end-to-end-supply-chain/securing-builds)"
|
||||
|
|
|
|||
|
|
@ -142,4 +142,4 @@ For more information about viewing pull requests opened by {% data variables.pro
|
|||
|
||||
For more information about the security advisories that contribute to {% data variables.product.prodname_dependabot_alerts %}, see "[AUTOTITLE](/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/browsing-security-advisories-in-the-github-advisory-database)."
|
||||
|
||||
For more information about configuring notifications about {% data variables.product.prodname_dependabot_alerts %}, see "[AUTOTITLE](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts)."
|
||||
For more information about configuring notifications about {% data variables.product.prodname_dependabot_alerts %}, see "[AUTOTITLE](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts)."
|
||||
|
|
|
|||
|
|
@ -29,4 +29,4 @@ You can enable push protection for yourself through your personal account settin
|
|||
{% data reusables.user-settings.security-analysis %}
|
||||
1. Under "User", to the right of "Push protection for yourself", click **Enable**.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -39,4 +39,4 @@ The metrics are based on activity from the last 30 days.
|
|||
{% data reusables.organizations.navigate-to-org %}
|
||||
{% data reusables.organizations.security-overview %}
|
||||
1. In the sidebar, under "Metrics", click **{% octicon "graph" aria-hidden="true" %} {% data variables.product.prodname_secret_scanning_caps %}**.
|
||||
1. Click on an individual secret type or repository to see the associated {% data variables.secret-scanning.alerts %} for your organization.
|
||||
1. Click on an individual secret type or repository to see the associated {% data variables.secret-scanning.alerts %} for your organization.
|
||||
|
|
|
|||
|
|
@ -167,4 +167,4 @@ For more information, see [`gh codespace code`](https://cli.github.com/manual/gh
|
|||
|
||||
## Further reading
|
||||
|
||||
- "[AUTOTITLE](/rest/codespaces)" (REST API reference)
|
||||
- "[AUTOTITLE](/rest/codespaces)" (REST API reference)
|
||||
|
|
|
|||
|
|
@ -265,4 +265,4 @@ You can use the {% data variables.product.prodname_cli %} extension to create a
|
|||
gh codespace edit -m MACHINE-TYPE-NAME
|
||||
```
|
||||
|
||||
For more information, see the "{% data variables.product.prodname_cli %}" tab of "[AUTOTITLE](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace)."
|
||||
For more information, see the "{% data variables.product.prodname_cli %}" tab of "[AUTOTITLE](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace)."
|
||||
|
|
|
|||
|
|
@ -92,4 +92,4 @@ If you change from **user ownership** to **organization ownership**, existing co
|
|||
|
||||
{% data reusables.codespaces.codespaces-spending-limit-requirement %}
|
||||
|
||||
For information on managing and changing your account's spending limit, see "[AUTOTITLE](/billing/managing-billing-for-github-codespaces/managing-the-spending-limit-for-github-codespaces#managing-the-github-codespaces-spending-limit-for-your-organization-account)."
|
||||
For information on managing and changing your account's spending limit, see "[AUTOTITLE](/billing/managing-billing-for-github-codespaces/managing-the-spending-limit-for-github-codespaces#managing-the-github-codespaces-spending-limit-for-your-organization-account)."
|
||||
|
|
|
|||
|
|
@ -71,4 +71,4 @@ Once a user loses access to a codespace, the codespace is retained for a period
|
|||
{% data reusables.organizations.click-general %}
|
||||
1. On the {% data variables.product.prodname_codespaces %} settings page, under "Codespaces access," select your preferred setting for {% data variables.product.prodname_github_codespaces %} in your organization's private {% ifversion ghec %}and internal {% endif %}repositories.
|
||||
|
||||
You can disable {% data variables.product.prodname_codespaces %}, enable for specific members, enable for all members, or enable for all members and collaborators.
|
||||
You can disable {% data variables.product.prodname_codespaces %}, enable for specific members, enable for all members, or enable for all members and collaborators.
|
||||
|
|
|
|||
|
|
@ -14,4 +14,4 @@ Before you submit your changes to the {% data variables.product.prodname_docs %}
|
|||
- Review your entire pull request to ensure it follows our guidance on creating content that can be translated. For more information, see "[AUTOTITLE](/contributing/writing-for-github-docs/writing-content-to-be-translated)."
|
||||
- Check your changes for grammar, spelling, and adherence to the style guide. For more information, see "[AUTOTITLE](/contributing/writing-for-github-docs/style-guide)."
|
||||
- If you have added new versioning or made changes to existing versioning, confirm your changes render as expected while viewing each available version of the article.
|
||||
- If there are any failing checks in your pull request, troubleshoot them until they're all passing.
|
||||
- If there are any failing checks in your pull request, troubleshoot them until they're all passing.
|
||||
|
|
|
|||
|
|
@ -106,4 +106,4 @@ If your text or code example includes content between curly brackets (`{` and `}
|
|||
|
||||
<pre>
|
||||
GITHUB_TOKEN: ${% raw %}${{ secrets.GITHUB_TOKEN }}${% endraw %}
|
||||
</pre>
|
||||
</pre>
|
||||
|
|
|
|||
|
|
@ -322,4 +322,4 @@ Sometimes a change isn't included in the release it was originally intended for.
|
|||
|
||||
### Test, test, and test again
|
||||
|
||||
Whether you're writing the content or reviewing the content, pay attention to the content design plan and affected products, and check the rendered content in a staging or development environment to ensure that the content describes each product accurately.
|
||||
Whether you're writing the content or reviewing the content, pay attention to the content design plan and affected products, and check the rendered content in a staging or development environment to ensure that the content describes each product accurately.
|
||||
|
|
|
|||
|
|
@ -221,4 +221,4 @@ Your Liquid conditional would look like this:
|
|||
|
||||
When the 3.10 release is deprecated, the `/assets/images/enterprise/3.10` directory will be removed.
|
||||
|
||||
The numbered release directory should contain images that apply to that release number only or to that release number and earlier. For example, images in `/assets/images/enterprise/2.22` should contain images that apply to 2.22 only or 2.22 and earlier.
|
||||
The numbered release directory should contain images that apply to that release number only or to that release number and earlier. For example, images in `/assets/images/enterprise/2.22` should contain images that apply to 2.22 only or 2.22 and earlier.
|
||||
|
|
|
|||
|
|
@ -377,4 +377,4 @@ Include an example of restoring cached dependencies. We'll want to link out to t
|
|||
{% comment %}
|
||||
This section can simply link out to https://docs.github.com/en/actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts or provide additional information about which artifacts might be typical to upload for a CI workflow.
|
||||
{% endcomment %}{% endraw %}
|
||||
```
|
||||
```
|
||||
|
|
|
|||
|
|
@ -157,4 +157,4 @@ Generally, if you're using company equipment, your company's IT department shoul
|
|||
- For macOS, see [Add certificates to a keychain using Keychain Access on Mac](https://support.apple.com/en-gb/guide/keychain-access/kyca2431/mac) in the Keychain Access User Guide.
|
||||
- For Linux, see [Installing a root CA certificate in the trust store](https://ubuntu.com/server/docs/security-trust-store) in the Ubuntu documentation. Similar instructions should apply to most Linux distributions.
|
||||
|
||||
If you have installed a certificate but {% data variables.product.prodname_copilot_short %} isn't detecting it, see "[AUTOTITLE](/copilot/troubleshooting-github-copilot/troubleshooting-network-errors-for-github-copilot#troubleshooting-certificate-related-errors)."
|
||||
If you have installed a certificate but {% data variables.product.prodname_copilot_short %} isn't detecting it, see "[AUTOTITLE](/copilot/troubleshooting-github-copilot/troubleshooting-network-errors-for-github-copilot#troubleshooting-certificate-related-errors)."
|
||||
|
|
|
|||
|
|
@ -120,4 +120,4 @@ One of the limitations of {% data variables.product.prodname_copilot_chat_short
|
|||
## Further reading
|
||||
|
||||
- [AUTOTITLE](/free-pro-team@latest/site-policy/github-terms/github-copilot-pre-release-terms)
|
||||
- [{% data variables.product.prodname_copilot %} Trust Center](https://resources.github.com/copilot-trust-center/)
|
||||
- [{% data variables.product.prodname_copilot %} Trust Center](https://resources.github.com/copilot-trust-center/)
|
||||
|
|
|
|||
|
|
@ -50,4 +50,4 @@ To give people or teams within your organization access to {% data variables.pro
|
|||
If members of your organization will be using {% data variables.product.prodname_copilot %} on your company's corporate network, you may need to configure network settings so that members can use {% data variables.product.prodname_copilot %} successfully.
|
||||
|
||||
- If you use an HTTP proxy server on your network, you can configure {% data variables.product.prodname_copilot %} to connect via this server. To successfully intercept and inspect {% data variables.product.prodname_copilot %}'s secure connection, you may need to install custom SSL certificates on your users' machines. For more information, see "[AUTOTITLE](/copilot/configuring-github-copilot/configuring-network-settings-for-github-copilot)."
|
||||
- If you use a firewall, you may need to add certain domains to the firewall's allowlist. For more information, see "[AUTOTITLE](/copilot/troubleshooting-github-copilot/troubleshooting-firewall-settings-for-github-copilot)."
|
||||
- If you use a firewall, you may need to add certain domains to the firewall's allowlist. For more information, see "[AUTOTITLE](/copilot/troubleshooting-github-copilot/troubleshooting-firewall-settings-for-github-copilot)."
|
||||
|
|
|
|||
|
|
@ -100,4 +100,4 @@ You can review usage data for {% data variables.product.prodname_copilot_for_bus
|
|||
|
||||
## Further reading
|
||||
|
||||
- "[AUTOTITLE](/free-pro-team@latest/site-policy/privacy-policies/github-copilot-for-business-privacy-statement)"
|
||||
- "[AUTOTITLE](/free-pro-team@latest/site-policy/privacy-policies/github-copilot-for-business-privacy-statement)"
|
||||
|
|
|
|||
|
|
@ -37,4 +37,4 @@ shortTitle: Managing policies
|
|||
|
||||
## Further reading
|
||||
|
||||
- "[AUTOTITLE](/free-pro-team@latest/site-policy/privacy-policies/github-copilot-for-business-privacy-statement)"
|
||||
- "[AUTOTITLE](/free-pro-team@latest/site-policy/privacy-policies/github-copilot-for-business-privacy-statement)"
|
||||
|
|
|
|||
|
|
@ -36,4 +36,4 @@ If you are experiencing authentication issues after installing the {% data varia
|
|||
|
||||
|
||||
|
||||
{% endvisualstudio %}
|
||||
{% endvisualstudio %}
|
||||
|
|
|
|||
|
|
@ -74,4 +74,4 @@ Some possible ways to resolve certificate-related errors are:
|
|||
|
||||
**Warning:** Ignoring certificate errors can cause security issues and is not recommended.
|
||||
|
||||
{% endwarning %}
|
||||
{% endwarning %}
|
||||
|
|
|
|||
|
|
@ -40,4 +40,4 @@ Each commit shows:
|
|||
|
||||
## Further reading
|
||||
|
||||
- "[AUTOTITLE](/desktop/working-with-your-remote-repository-on-github-or-github-enterprise/syncing-your-branch-in-github-desktop)"
|
||||
- "[AUTOTITLE](/desktop/working-with-your-remote-repository-on-github-or-github-enterprise/syncing-your-branch-in-github-desktop)"
|
||||
|
|
|
|||
|
|
@ -26,4 +26,4 @@ If you're interested in the open source {% data variables.product.prodname_deskt
|
|||
|
||||
## Further reading
|
||||
|
||||
- "[AUTOTITLE](/get-started/using-git/about-git)"
|
||||
- "[AUTOTITLE](/get-started/using-git/about-git)"
|
||||
|
|
|
|||
|
|
@ -52,4 +52,4 @@ Some features are supported for additional languages or package managers. If you
|
|||
- PHP and Scala are supported for {% data variables.product.prodname_code_scanning %} by third-party actions.
|
||||
{% endif %}
|
||||
|
||||
{% endnote %}
|
||||
{% endnote %}
|
||||
|
|
|
|||
|
|
@ -41,4 +41,4 @@ To view help for a particular subcommand, use the `--help` flag.
|
|||
gh COMMAND [SUBCOMMAND ...] --help
|
||||
```
|
||||
|
||||
All of the information that's available by running these commands in the terminal is also included in the [{% data variables.product.prodname_cli %} online manual](https://cli.github.com/manual/gh).
|
||||
All of the information that's available by running these commands in the terminal is also included in the [{% data variables.product.prodname_cli %} online manual](https://cli.github.com/manual/gh).
|
||||
|
|
|
|||
|
|
@ -34,4 +34,4 @@ Tasklists add support for hierarchies of issues on {% data variables.product.pro
|
|||
|
||||
You can create a tasklist using Markdown or using the {% data variables.product.product_name %} UI. Regardless of how you created your tasklist, you can edit it using either Markdown or the UI. For more information, see "[AUTOTITLE](/issues/managing-your-tasks-with-tasklists/creating-a-tasklist)" and "[AUTOTITLE](/issues/managing-your-tasks-with-tasklists/managing-tasks-in-a-tasklist)."
|
||||
|
||||
Tasklists also integrate with your projects. {% ifversion projects-v2-tasklists-without-breadcrumbs %}You can{% else %}When you click on an issue in your project, the side-panel opens and displays the issue's place in the hierarchy on a breadcrumb menu, allowing you to navigate through the issues included in your tasklists. You can also{% endif %} add the "Tracks" and "Tracked-by fields" to your project views to quickly see the relationships between your issues. For information, see "[AUTOTITLE](/issues/managing-your-tasks-with-tasklists/using-projects-and-tasklists)."
|
||||
Tasklists also integrate with your projects. {% ifversion projects-v2-tasklists-without-breadcrumbs %}You can{% else %}When you click on an issue in your project, the side-panel opens and displays the issue's place in the hierarchy on a breadcrumb menu, allowing you to navigate through the issues included in your tasklists. You can also{% endif %} add the "Tracks" and "Tracked-by fields" to your project views to quickly see the relationships between your issues. For information, see "[AUTOTITLE](/issues/managing-your-tasks-with-tasklists/using-projects-and-tasklists)."
|
||||
|
|
|
|||
|
|
@ -15,4 +15,4 @@ children:
|
|||
- /using-projects-and-tasklists
|
||||
---
|
||||
|
||||
{% data reusables.projects.tasklists-release-stage %}
|
||||
{% data reusables.projects.tasklists-release-stage %}
|
||||
|
|
|
|||
|
|
@ -66,4 +66,4 @@ You can remove issues, pull requests, and draft tasks from your tasklist. Issues
|
|||
|
||||
|
||||
|
||||
1. In the menu, click **Remove**.
|
||||
1. In the menu, click **Remove**.
|
||||
|
|
|
|||
|
|
@ -162,4 +162,4 @@ Issues and pull requests are not automatically added to a project when they are
|
|||
|
||||
After following this guide, you have created a tracking issue with two tasklists, made changes to those tasklists in the UI and directly with Markdown, converted a draft task into an issue, and integrated your tasklist data with a project.
|
||||
|
||||
To learn more about managing the items in your tasklist, see "[AUTOTITLE](/issues/managing-your-tasks-with-tasklists/managing-tasks-in-a-tasklist)." For more information on integrating tasklists with your projects, see "[AUTOTITLE](/issues/managing-your-tasks-with-tasklists/using-projects-and-tasklists)."
|
||||
To learn more about managing the items in your tasklist, see "[AUTOTITLE](/issues/managing-your-tasks-with-tasklists/managing-tasks-in-a-tasklist)." For more information on integrating tasklists with your projects, see "[AUTOTITLE](/issues/managing-your-tasks-with-tasklists/using-projects-and-tasklists)."
|
||||
|
|
|
|||
|
|
@ -57,4 +57,4 @@ When the issues added to your project are either tracked by tasklists or contain
|
|||
|
||||
|
||||
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -43,4 +43,4 @@ All of these tools import source code and revision history, only. If you also wa
|
|||
## Further reading
|
||||
|
||||
- "[AUTOTITLE](/get-started/using-git/troubleshooting-the-2-gb-push-limit)"
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -65,4 +65,4 @@ To follow these steps, you must use a macOS or Linux system and have the followi
|
|||
## Further reading
|
||||
|
||||
- "[AUTOTITLE](/get-started/using-git/troubleshooting-the-2-gb-push-limit)"
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -61,4 +61,4 @@ To follow these steps, you must use a macOS or Linux system and have the followi
|
|||
## Further reading
|
||||
|
||||
- "[AUTOTITLE](/get-started/using-git/troubleshooting-the-2-gb-push-limit)"
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -65,4 +65,4 @@ To follow these steps, you must use Windows and have the following tools install
|
|||
## Further reading
|
||||
|
||||
- "[AUTOTITLE](/get-started/using-git/troubleshooting-the-2-gb-push-limit)"
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -59,4 +59,4 @@ If the repository you are importing contains large files, you may run into a war
|
|||
## Further reading
|
||||
|
||||
- "[AUTOTITLE](/get-started/using-git/troubleshooting-the-2-gb-push-limit)"
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -177,4 +177,4 @@ There are limits to what {% data variables.product.prodname_importer_proper_name
|
|||
- **{% data variables.large_files.product_name_short %} objects not migrated**: The {% data variables.product.prodname_importer_secondary_name %} can migrate repositories that use {% data variables.large_files.product_name_short %}, but the LFS objects themselves will not be migrated. They can be pushed to your migration destination as a follow-up task after the migration is complete. For more information, see "[AUTOTITLE](/repositories/creating-and-managing-repositories/duplicating-a-repository#mirroring-a-repository-that-contains-git-large-file-storage-objects)."
|
||||
- **Follow-up tasks required:** When migrating between {% data variables.product.prodname_dotcom %} products, certain settings are not migrated and must be reconfigured in the new repository. For a list of follow-up tasks you'll need to complete after each migration, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/migrating-between-github-products-with-github-enterprise-importer#completing-follow-up-tasks)."
|
||||
- **Delayed code search functionality:** Re-indexing the search index can take a few hours after a repository is migrated, and code searches may return unexpected results until re-indexing is complete.
|
||||
- **Rulesets configured for your organization can cause migrations to fail**: For example, if you configured a rule that requires email addresses for commit authors to end with `@monalisa.cat`, and the repository you're migrating contains commits that don't comply with this rule, your migration will fail. For more information about rulesets, see "[AUTOTITLE](/enterprise-cloud@latest/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets)."
|
||||
- **Rulesets configured for your organization can cause migrations to fail**: For example, if you configured a rule that requires email addresses for commit authors to end with `@monalisa.cat`, and the repository you're migrating contains commits that don't comply with this rule, your migration will fail. For more information about rulesets, see "[AUTOTITLE](/enterprise-cloud@latest/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets)."
|
||||
|
|
|
|||
|
|
@ -45,4 +45,4 @@ You should ensure that 2FA is enabled for unattended or shared access accounts i
|
|||
1. Copy the secret that's displayed in the dialog box.
|
||||
1. Reconfigure 2FA using the copied secret.
|
||||
1. Select a CLI app (such as oathtool) for generating TOTP codes from the TOTP secret. You will use the app to generate a new TOTP code from the TOTP secret every time you need to access the account. For more information, see [oathtool](https://www.nongnu.org/oath-toolkit/man-oathtool.html) in the OATH Toolkit documentation.
|
||||
1. When you need to access the account, use the password reset functionality to reset the password (via the mailing list), and use the CLI app to generate a TOTP code.
|
||||
1. When you need to access the account, use the password reset functionality to reset the password (via the mailing list), and use the CLI app to generate a TOTP code.
|
||||
|
|
|
|||
|
|
@ -83,4 +83,4 @@ If an organization member was removed from the organization because they did not
|
|||
{% endif %}
|
||||
{% ifversion fpt or ghec %}
|
||||
{% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %}
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -90,4 +90,4 @@ To target all repositories in your organization, in the "Target repositories" se
|
|||
|
||||
## About regular expressions for commit metadata
|
||||
|
||||
{% data reusables.repositories.rulesets-commit-regex %}
|
||||
{% data reusables.repositories.rulesets-commit-regex %}
|
||||
|
|
|
|||
|
|
@ -22,4 +22,4 @@ Organization owners can use one of their downloaded or saved recovery codes to b
|
|||
## Using a recovery code
|
||||
|
||||
1. Attempt to access the organization.
|
||||
{% data reusables.saml.recovery-code-access %}
|
||||
{% data reusables.saml.recovery-code-access %}
|
||||
|
|
|
|||
|
|
@ -22,4 +22,4 @@ After you disable SAML SSO for your organization, all external identities for yo
|
|||
{% endnote %}
|
||||
{% data reusables.organizations.security %}
|
||||
1. Under "SAML single sign-on", deselect **Enable SAML authentication**.
|
||||
1. Click **Save**.
|
||||
1. Click **Save**.
|
||||
|
|
|
|||
|
|
@ -42,4 +42,4 @@ If a team has direct access to a repository, you can remove that team's access t
|
|||
|
||||
## Further reading
|
||||
|
||||
- "[AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization)"
|
||||
- "[AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization)"
|
||||
|
|
|
|||
|
|
@ -65,4 +65,4 @@ User Engagement Data is used by GitHub, and Microsoft to provide the service and
|
|||
|
||||
User engagement data (which includes pseudonymous identifiers and general usage data), is required for the use of GitHub Copilot and will continue to be collected, processed, and shared with Microsoft when you use GitHub Copilot.
|
||||
|
||||
For more information on how GitHub processes and uses personal data, please see the [GitHub Privacy Statement](/site-policy/privacy-policies/github-privacy-statement).
|
||||
For more information on how GitHub processes and uses personal data, please see the [GitHub Privacy Statement](/site-policy/privacy-policies/github-privacy-statement).
|
||||
|
|
|
|||
|
|
@ -101,4 +101,4 @@ You can subscribe your {% data variables.product.prodname_github_app %} to webho
|
|||
|
||||
## Further reading
|
||||
|
||||
- "[AUTOTITLE](/webhooks/using-webhooks/handling-webhook-deliveries)"
|
||||
- "[AUTOTITLE](/webhooks/using-webhooks/handling-webhook-deliveries)"
|
||||
|
|
|
|||
|
|
@ -72,4 +72,4 @@ You can disable webhooks that were previously enabled for events relating to {%
|
|||
|
||||
## Disabling webhooks for a {% data variables.product.prodname_github_app %}
|
||||
|
||||
You can disable webhook deliveries to your {% data variables.product.prodname_github_app %}, or change the events it subscribes to. For more information, see "[AUTOTITLE](/apps/maintaining-github-apps/modifying-a-github-app-registration#activating-or-deactivating-the-github-app-webhook)."
|
||||
You can disable webhook deliveries to your {% data variables.product.prodname_github_app %}, or change the events it subscribes to. For more information, see "[AUTOTITLE](/apps/maintaining-github-apps/modifying-a-github-app-registration#activating-or-deactivating-the-github-app-webhook)."
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
Choose a recovery verification factor.
|
||||
- If you've used your current device to log into this account before and would like to use the device for verification, click **Verify with this device**. Device verification is recorded with cookies, and won't be available if your browser deletes cookies regularly.
|
||||
- If you've previously set up an SSH key on this account and would like to use the SSH key for verification, click **SSH key**.
|
||||
- If you've previously set up a {% data variables.product.pat_generic %} and would like to use the {% data variables.product.pat_generic %} for verification, click **{% data variables.product.pat_generic_caps %}**.
|
||||
- If you've previously set up a {% data variables.product.pat_generic %} and would like to use the {% data variables.product.pat_generic %} for verification, click **{% data variables.product.pat_generic_caps %}**.
|
||||
|
|
|
|||
|
|
@ -2,4 +2,4 @@
|
|||
|
||||
- Tips and tricks for getting started with your account
|
||||
- Customized information about engaging projects or new features
|
||||
- Newsletters that you've subscribed to
|
||||
- Newsletters that you've subscribed to
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
A member of {% data variables.contact.github_support %} will review your request and email you within three business days. If your request is approved, you'll receive a link to complete your account recovery process. If your request is denied, the email will include a way to contact support with any additional questions.
|
||||
A member of {% data variables.contact.github_support %} will review your request and email you within three business days. If your request is approved, you'll receive a link to complete your account recovery process. If your request is denied, the email will include a way to contact support with any additional questions.
|
||||
|
|
|
|||
|
|
@ -8,4 +8,4 @@
|
|||
|
||||
|
||||
1. To finish unlinking your email, on {% data variables.product.prodname_dotcom_the_website %}, click **Unlink**.
|
||||
1. Optionally, to create a new account and link your newly unlinked email, click **Create a new account**.
|
||||
1. Optionally, to create a new account and link your newly unlinked email, click **Create a new account**.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
You can deliver deployments through {% data variables.product.prodname_actions %} and environments or with the REST API and third party apps. For more information about using environments to deploy with {% data variables.product.prodname_actions %}, see "[AUTOTITLE](/actions/deployment/targeting-different-environments/using-environments-for-deployment)." For more information about deployments with the REST API, see "[AUTOTITLE](/rest/repos#deployments)."
|
||||
You can deliver deployments through {% data variables.product.prodname_actions %} and environments or with the REST API and third party apps. For more information about using environments to deploy with {% data variables.product.prodname_actions %}, see "[AUTOTITLE](/actions/deployment/targeting-different-environments/using-environments-for-deployment)." For more information about deployments with the REST API, see "[AUTOTITLE](/rest/repos#deployments)."
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
By default, repositories in an organization do not have access to enterprise-level runner groups. To give repositories access to enterprise runner groups, organization owners must configure each enterprise runner group and choose which repositories have access.
|
||||
By default, repositories in an organization do not have access to enterprise-level runner groups. To give repositories access to enterprise runner groups, organization owners must configure each enterprise runner group and choose which repositories have access.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
{% data variables.actions.hosted_runner_caps %}s are only billed at the per-minute rate for the amount of time workflows are executed on them. There is no cost associated with creating a {% data variables.actions.hosted_runner %} that is not being used by a workflow.
|
||||
{% data variables.actions.hosted_runner_caps %}s are only billed at the per-minute rate for the amount of time workflows are executed on them. There is no cost associated with creating a {% data variables.actions.hosted_runner %} that is not being used by a workflow.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
In addition to the [standard {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources), {% data variables.product.prodname_dotcom %} offers customers on {% data variables.product.prodname_team %} and {% data variables.product.prodname_ghe_cloud %} plans a range of managed virtual machines with more RAM, CPU, and disk space. These runners are hosted by {% data variables.product.prodname_dotcom %} and have the runner application and other tools preinstalled.
|
||||
In addition to the [standard {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources), {% data variables.product.prodname_dotcom %} offers customers on {% data variables.product.prodname_team %} and {% data variables.product.prodname_ghe_cloud %} plans a range of managed virtual machines with more RAM, CPU, and disk space. These runners are hosted by {% data variables.product.prodname_dotcom %} and have the runner application and other tools preinstalled.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
If you don't specify a runner group during the registration process, your new runners are automatically assigned to the default group, and can then be moved to another group.
|
||||
If you don't specify a runner group during the registration process, your new runners are automatically assigned to the default group, and can then be moved to another group.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
By default, all repositories in an organization are granted access to organization-level runner groups. To restrict which repositories have access, organization owners must configure organization runner groups and choose which repositories have access.
|
||||
By default, all repositories in an organization are granted access to organization-level runner groups. To restrict which repositories have access, organization owners must configure organization runner groups and choose which repositories have access.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
In order to remove a runner group, you must first move or remove all of the runners from the group.
|
||||
In order to remove a runner group, you must first move or remove all of the runners from the group.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
You can configure a runner group to run either selected workflows or all workflows. For example, you might use this setting to protect secrets that are stored on runners or to standardize deployment workflows by restricting a runner group to run only a specific reusable workflow. This setting cannot be overridden if you are configuring an organization's runner group that was shared by an enterprise.
|
||||
You can configure a runner group to run either selected workflows or all workflows. For example, you might use this setting to protect secrets that are stored on runners or to standardize deployment workflows by restricting a runner group to run only a specific reusable workflow. This setting cannot be overridden if you are configuring an organization's runner group that was shared by an enterprise.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
If you have `repo: write` access to a repository, you can view a list of the runners available to the repository.
|
||||
If you have `repo: write` access to a repository, you can view a list of the runners available to the repository.
|
||||
|
|
|
|||
|
|
@ -2,4 +2,4 @@
|
|||
|
||||
**Note:** Enterprise and organization owners with privileges to create runners have the option to create new runners from this page. If you are an enterprise or organization owner, click **New runner** at the top right of the list of runners to add runners to the repository. For more information, see {% ifversion actions-hosted-runners %}"[AUTOTITLE](/actions/using-github-hosted-runners/managing-larger-runners)" and {% endif %}"[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/adding-self-hosted-runners)."
|
||||
|
||||
{% endnote %}
|
||||
{% endnote %}
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
{% data variables.product.prodname_dotcom %} recommends pinning actions to a commit SHA. To get a newer version, you will need to update the SHA. You can also reference a tag or branch, but the action may change without warning.
|
||||
{% data variables.product.prodname_dotcom %} recommends pinning actions to a commit SHA. To get a newer version, you will need to update the SHA. You can also reference a tag or branch, but the action may change without warning.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
If you are using Azure and {% data variables.product.prodname_ghe_cloud %}, you can create {% data variables.product.company_short %}-hosted runners in your Azure VNET(s). This enables you to take advantage of {% data variables.product.company_short %}-managed infrastructure for your CI/CD while providing you with full control over the networking policies of your runners. For more information about Azure VNET, see [What is Azure Virtual Network?](https://learn.microsoft.com/en-us/azure/virtual-network/virtual-networks-overview) in the Azure documentation.
|
||||
If you are using Azure and {% data variables.product.prodname_ghe_cloud %}, you can create {% data variables.product.company_short %}-hosted runners in your Azure VNET(s). This enables you to take advantage of {% data variables.product.company_short %}-managed infrastructure for your CI/CD while providing you with full control over the networking policies of your runners. For more information about Azure VNET, see [What is Azure Virtual Network?](https://learn.microsoft.com/en-us/azure/virtual-network/virtual-networks-overview) in the Azure documentation.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
Once a repository has reached its maximum cache storage, the cache eviction policy will create space by deleting the oldest caches in the repository.
|
||||
Once a repository has reached its maximum cache storage, the cache eviction policy will create space by deleting the oldest caches in the repository.
|
||||
|
|
|
|||
|
|
@ -9,4 +9,4 @@ Always include a security admonition above this procedure. This is either one of
|
|||
1. Under "Organization access," use the dropdown menu to click **Selected organizations**.
|
||||
1. To the right of the dropdown menu, click {% octicon "gear" aria-label="The Gear icon" %}.
|
||||
1. In the popup, use the checkboxes to select organizations that can use this runner group.
|
||||
1. Click **Save group**.
|
||||
1. Click **Save group**.
|
||||
|
|
|
|||
|
|
@ -10,4 +10,4 @@ Always include a security admonition above this procedure. This is either one of
|
|||
1. Under "Repository access," use the dropdown menu to click **Selected organizations**.
|
||||
1. To the right of the dropdown menu, click {% octicon "gear" aria-label="The Gear icon" %}.
|
||||
1. In the popup, use the checkboxes to select repositories that can access this runner group.
|
||||
1. Click **Save group**.
|
||||
1. Click **Save group**.
|
||||
|
|
|
|||
|
|
@ -15,4 +15,4 @@ Always include a security admonition above this procedure. This is either one of
|
|||
|
||||
Organization-owned runner groups cannot access workflows from a different organization in the enterprise; instead, you must create an enterprise-owned runner group.
|
||||
|
||||
1. Click **Save**.
|
||||
1. Click **Save**.
|
||||
|
|
|
|||
|
|
@ -1,2 +1,2 @@
|
|||
1. In the "Auto-scaling" section, under "Maximum Job Concurrency," enter the maximum number of jobs you would like to allow to run at the same time.
|
||||
1. Click **Save**.
|
||||
1. Click **Save**.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
1. Optionally, to copy a runner's label to use it in a workflow, click {% octicon "kebab-horizontal" aria-label="More options" %} to the right of the runner, then click **Copy label**.
|
||||
1. Optionally, to copy a runner's label to use it in a workflow, click {% octicon "kebab-horizontal" aria-label="More options" %} to the right of the runner, then click **Copy label**.
|
||||
|
|
|
|||
Некоторые файлы не были показаны из-за слишком большого количества измененных файлов Показать больше
Загрузка…
Ссылка в новой задаче