зеркало из https://github.com/github/docs.git
Make more images accessible in the `images/help/settings` directory (#36562)
This commit is contained in:
Laura Coursen
GitHub
Родитель
1bf87f06de
Коммит
30862e2bc9
|
|
@ -41,8 +41,6 @@ You can configure your CI workflow to run when a {% data variables.product.prodn
|
|||
|
||||
When you set up CI in your repository, {% data variables.product.product_name %} analyzes the code in your repository and recommends CI workflows based on the language and framework in your repository. For example, if you use [Node.js](https://nodejs.org/en/), {% data variables.product.product_name %} will suggest a starter workflow that installs your Node.js packages and runs your tests. You can use the CI starter workflow suggested by {% data variables.product.product_name %}, customize the suggested starter workflow, or create your own custom workflow file to run your CI tests.
|
||||
|
||||
|
||||
|
||||
In addition to helping you set up CI workflows for your project, you can use {% data variables.product.prodname_actions %} to create workflows across the full software development life cycle. For example, you can use actions to deploy, package, or release your project. For more information, see "[AUTOTITLE](/actions/learn-github-actions)."
|
||||
|
||||
For a definition of common terms, see "[AUTOTITLE](/actions/learn-github-actions/understanding-github-actions)."
|
||||
|
|
|
|||
|
|
@ -162,6 +162,5 @@ You can view the results from your previous attempts at running a workflow. You
|
|||
|
||||
{%- else %}
|
||||
1. In the left pane, click a previous run attempt.
|
||||
|
||||
{%- endif %}
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -212,9 +212,7 @@ You can check which access policies are being applied to a secret in your organi
|
|||
{% data reusables.organizations.navigate-to-org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.actions.sidebar-secrets-and-variables %}
|
||||
1. The list of secrets includes any configured permissions and policies. For example:
|
||||
|
||||
1. For more details on the configured permissions for each secret, click **Update**.
|
||||
1. The list of secrets includes any configured permissions and policies. For more details about the configured permissions for each secret, click **Update**.
|
||||
|
||||
## Using encrypted secrets in a workflow
|
||||
|
||||
|
|
|
|||
|
|
@ -17,8 +17,6 @@ You can get a list of all jobs currently running on {% data variables.product.pr
|
|||
{% data reusables.actions.github-hosted-runners-table-entry %}
|
||||
1. Review the "Active jobs" section, which contains a list of all jobs currently running on {% data variables.product.prodname_dotcom %}-hosted runners.
|
||||
|
||||
|
||||
|
||||
## Viewing queued jobs in your organization or enterprise
|
||||
|
||||
{% data variables.product.prodname_dotcom %}-hosted runners allow you to run jobs concurrently, and the maximum number of concurrent jobs will vary depending on your plan. If you reach the maximum number of concurrent jobs, any new jobs will start to enter a queue. To find out more about the number of concurrent jobs available to your plan, see "[AUTOTITLE](/actions/learn-github-actions/usage-limits-billing-and-administration)."
|
||||
|
|
|
|||
|
|
@ -52,7 +52,6 @@ You should plan where you'll store your secrets. We recommend storing secrets in
|
|||
|
||||
In {% data variables.product.prodname_dotcom %}, you can store secrets at the repository or organization level. Secrets at the repository level can be limited to workflows in certain environments, such as production or testing. For more information, see "[AUTOTITLE](/actions/security-guides/encrypted-secrets)."
|
||||
|
||||
|
||||
You should consider adding manual approval protection for sensitive environments, so that workflows must be approved before getting access to the environments' secrets. For more information, see "[AUTOTITLE](/actions/deployment/targeting-different-environments/using-environments-for-deployment)."
|
||||
|
||||
### Security considerations for third-party actions
|
||||
|
|
|
|||
|
|
@ -123,16 +123,6 @@ By default, when you create a new enterprise, `GITHUB_TOKEN` only has read acces
|
|||
{% data reusables.enterprise-accounts.policies-tab %}
|
||||
{% data reusables.enterprise-accounts.actions-tab %}
|
||||
1. Under "Workflow permissions", choose whether you want the `GITHUB_TOKEN` to have read and write access for all scopes, or just read access for the `contents` {% ifversion actions-default-workflow-permissions-restrictive %}and `packages` scopes{% else %}scope{% endif %}.
|
||||
|
||||
{% ifversion allow-actions-to-approve-pr-with-ent-repo %}
|
||||
{% ifversion actions-default-workflow-permissions-restrictive %}
|
||||
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
1. Click **Save** to apply the settings.
|
||||
|
||||
{% ifversion allow-actions-to-approve-pr-with-ent-repo %}
|
||||
|
|
@ -148,12 +138,6 @@ By default, when you create a new enterprise, workflows are not allowed to creat
|
|||
{% data reusables.enterprise-accounts.policies-tab %}
|
||||
{% data reusables.enterprise-accounts.actions-tab %}
|
||||
1. Under "Workflow permissions", use the **Allow GitHub Actions to create and approve pull requests** setting to configure whether `GITHUB_TOKEN` can create and approve pull requests.
|
||||
|
||||
{% ifversion actions-default-workflow-permissions-restrictive %}
|
||||
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
1. Click **Save** to apply the settings.
|
||||
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -23,7 +23,6 @@ When {% data variables.product.prodname_oauth_app %} access restrictions are ena
|
|||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.oauth_app_access %}
|
||||
1. Next to the application you'd like to approve, click **Review**.
|
||||
|
||||
1. After you review the information about the requested application, click **Grant access**.
|
||||
|
||||
## Further reading
|
||||
|
|
|
|||
|
|
@ -147,20 +147,6 @@ By default, when you create a new organization,{% ifversion ghec or ghes or ghae
|
|||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.settings-sidebar-actions-general %}
|
||||
1. Under "Workflow permissions", choose whether you want the `GITHUB_TOKEN` to have read and write access for all scopes, or just read access for the `contents` {% ifversion actions-default-workflow-permissions-restrictive %}and `packages` scopes{% else %}scope{% endif %}.
|
||||
|
||||
{% ifversion allow-actions-to-approve-pr %}
|
||||
{% ifversion allow-actions-to-approve-pr-with-ent-repo %}
|
||||
{% ifversion actions-default-workflow-permissions-restrictive %}
|
||||
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
1. Click **Save** to apply the settings.
|
||||
|
||||
{% ifversion allow-actions-to-approve-pr %}
|
||||
|
|
@ -175,17 +161,6 @@ By default, when you create a new organization, workflows are not allowed to {%
|
|||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.settings-sidebar-actions-general %}
|
||||
1. Under "Workflow permissions", use the **Allow GitHub Actions to {% ifversion allow-actions-to-approve-pr-with-ent-repo %}create and {% endif %}approve pull requests** setting to configure whether `GITHUB_TOKEN` can {% ifversion allow-actions-to-approve-pr-with-ent-repo %}create and {% endif %}approve pull requests.
|
||||
|
||||
{% ifversion allow-actions-to-approve-pr-with-ent-repo %}
|
||||
{% ifversion actions-default-workflow-permissions-restrictive %}
|
||||
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
1. Click **Save** to apply the settings.
|
||||
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -104,16 +104,6 @@ By default, when you create a new repository in your personal account, `GITHUB_T
|
|||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% data reusables.repositories.settings-sidebar-actions-general %}
|
||||
1. Under "Workflow permissions", choose whether you want the `GITHUB_TOKEN` to have read and write access for all scopes, or just read access for the `contents` {% ifversion actions-default-workflow-permissions-restrictive %}and `packages` scopes{% else %}scope{% endif %}.
|
||||
|
||||
{% ifversion allow-actions-to-approve-pr-with-ent-repo %}
|
||||
{% ifversion actions-default-workflow-permissions-restrictive %}
|
||||
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
1. Click **Save** to apply the settings.
|
||||
|
||||
{% ifversion allow-actions-to-approve-pr-with-ent-repo %}
|
||||
|
|
@ -129,12 +119,6 @@ By default, when you create a new repository in your personal account, workflows
|
|||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% data reusables.repositories.settings-sidebar-actions-general %}
|
||||
1. Under "Workflow permissions", use the **Allow GitHub Actions to create and approve pull requests** setting to configure whether `GITHUB_TOKEN` can create and approve pull requests.
|
||||
|
||||
{% ifversion actions-default-workflow-permissions-restrictive %}
|
||||
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
1. Click **Save** to apply the settings.
|
||||
{% endif %}
|
||||
|
||||
|
|
|
|||
|
|
@ -1,2 +1 @@
|
|||
1. In the "Runners" section of the settings page, next to the runner group you'd like to configure, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Edit name and [organization|repository] access**.
|
||||
|
||||
1. In the "Runners" section of the settings page, next to the runner group you'd like to configure, click {% octicon "kebab-horizontal" aria-label="Show options" %}, then click **Edit name and [organization|repository] access**.
|
||||
|
|
@ -1,10 +1,10 @@
|
|||
{% comment %}
|
||||
{% comment %}
|
||||
|
||||
Always include a security admonition above this procedure. This is either one of the following, depending on whether the context is self-hosted runners or larger runners.
|
||||
|
||||
{% data reusables.actions.self-hosted-runner-security-admonition %}
|
||||
{% data reusables.actions.hosted-runner-security-admonition %}
|
||||
|
||||
|
||||
{% endcomment %}
|
||||
|
||||
All organizations have a single default runner group. Organizations within an enterprise account can create additional groups. Organization admins can allow individual repositories access to a runner group. For information about how to create a runner group with the REST API, see "[AUTOTITLE](/rest/actions#self-hosted-runner-groups)."
|
||||
|
|
@ -22,17 +22,4 @@ When creating a group, you must choose a policy that defines which repositories{
|
|||
{% data reusables.actions.runner-group-assign-policy-repo %}
|
||||
{% data reusables.actions.runner-group-assign-policy-workflow %}{%- ifversion restrict-groups-to-workflows %} Organization-owned runner groups cannot access workflows from a different organization in the enterprise; instead, you must create an enterprise-owned runner group.{% endif %}
|
||||
{% data reusables.actions.create-runner-group %}
|
||||
{% elsif ghae < 3.4 %}
|
||||
{% data reusables.organizations.navigate-to-org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.organizations.settings-sidebar-actions-runner-groups %}
|
||||
1. Under {% ifversion ghes or ghae %}"Runners"{% endif %}, click **Add new**, and then **New group**.
|
||||
|
||||
|
||||
1. Enter a name for your runner group, and assign a policy for repository access.
|
||||
|
||||
You can configure a runner group to be accessible to a specific list of repositories, or to all repositories in the organization.{% ifversion ghec or ghes %} By default, only private repositories can access runners in a runner group, but you can override this. This setting can't be overridden if configuring an organization's runner group that was shared by an enterprise.{% endif %}
|
||||
|
||||
|
||||
1. Click **Save group** to create the group and apply the policy.
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -1,5 +1 @@
|
|||
To identify any constraints with concurrency or queuing, you can check how many jobs are currently being processed on the {% data variables.product.prodname_dotcom %}-hosted runners in your organization or enterprise.
|
||||
|
||||
|
||||
|
||||
For more information, see "[AUTOTITLE](/actions/using-github-hosted-runners/monitoring-your-current-jobs)."
|
||||
To identify any constraints with concurrency or queuing, you can check how many jobs are currently being processed on the {% data variables.product.prodname_dotcom %}-hosted runners in your organization or enterprise. For more information, see "[AUTOTITLE](/actions/using-github-hosted-runners/monitoring-your-current-jobs)."
|
||||
|
|
|
|||
|
|
@ -1,3 +0,0 @@
|
|||
1. Locate the runner you want to update, and click {% octicon "triangle-down" aria-label="The downward triangle" %} to view the label selection menu. This menu displays all the custom labels available to your runner. Labels already assigned to your runner have a {% octicon "check" aria-label="Check mark" %} next to them.
|
||||
|
||||
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
1. If your runner is in a group, locate the runner group and click {% octicon "chevron-down" aria-label="The downward chevron" %} to view the list of runners.
|
||||
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
1. Locate the runner you want to update, and click {% octicon "triangle-down" aria-label="The downward triangle" %} to view the label selection menu. This menu displays all the custom labels available to your self-hosted runner. Labels already assigned to your self-hosted runner have a {% octicon "check" aria-label="Check mark" %} next to them.
|
||||
|
||||
|
|
@ -1,15 +0,0 @@
|
|||
1. Under "Runners", locate the runner in the list. If your runner is in a group, click {% octicon "chevron-down" aria-label="The downwards chevron" %} to expand the list.
|
||||
1. Click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} next to the runner you want to remove, then click **Remove**.
|
||||
|
||||
|
||||
1. You will see instructions for removing the self-hosted runner. Complete either of the following steps to remove the runner, depending on whether it is still accessible:
|
||||
|
||||
* **If you have access to the runner machine:** Follow the on-screen instructions for your machine's operating system to run the removal command. The instructions include the required URL and an automatically-generated, time-limited token.
|
||||
|
||||
The removal command does the following tasks:
|
||||
|
||||
* Removes the runner from {% data variables.product.product_name %}.
|
||||
* Removes any self-hosted runner application configuration files on the machine.
|
||||
* Removes any services configured if not running in interactive mode.
|
||||
|
||||
* **If you don't have access to the machine:** Click **Yes, force remove this runner** to force {% data variables.product.product_name %} to remove the runner.
|
||||
Загрузка…
Ссылка в новой задаче