Make some images accessible in the images/help/settings directory (#36528)
Co-authored-by: Isaac Brown <101839405+isaacmbrown@users.noreply.github.com>
This commit is contained in:
Laura Coursen
Binary file not shown.
|
Before Width: | Height: | Size: 6.4 KiB After Width: | Height: | Size: 75 KiB |
@@ -25,11 +25,9 @@ Organization members can always request owner approval for {% data variables.pro
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.access_applications %}
|
||||
{% data reusables.user-settings.access_authorized_oauth_apps %}
|
||||
3. In the list of applications, click the name of the {% data variables.product.prodname_oauth_app %} you'd like to request access for.
|
||||
|
||||
4. Next to the organization you'd like the {% data variables.product.prodname_oauth_app %} to access, click **Request access**.
|
||||
|
||||
5. After you review the information about requesting {% data variables.product.prodname_oauth_app %} access, click **Request approval from owners**.
|
||||
1. In the list of applications, click the name of the {% data variables.product.prodname_oauth_app %} you'd like to request access for.
|
||||
1. Next to the organization you'd like the {% data variables.product.prodname_oauth_app %} to access, click **Request access**.
|
||||
1. After you review the information about requesting {% data variables.product.prodname_oauth_app %} access, click **Request approval from owners**.
|
||||
|
||||
## Further reading
|
||||
|
||||
|
||||
@@ -41,8 +41,6 @@ Anyone with write permission to a repository can set up {% data variables.produc
|
||||
{% data reusables.repositories.actions-tab %}
|
||||
1. If you already have a workflow in your repository, click **New workflow**.
|
||||
1. The "{% ifversion actions-starter-template-ui %}Choose a workflow{% else %}Choose a workflow template{% endif %}" page shows a selection of recommended starter workflows. Find the starter workflow that you want to use, then click {% ifversion actions-starter-template-ui %}**Configure**{% else %}**Set up this workflow**{% endif %}.{% ifversion actions-starter-template-ui %} To help you find the starter workflow that you want, you can search for keywords or filter by category.{% endif %}
|
||||
|
||||
{% ifversion actions-starter-template-ui %}{% else %}{% endif %}
|
||||
1. If the starter workflow contains comments detailing additional setup steps, follow these steps. Many of the starter workflow have corresponding guides. For more information, see the [{% data variables.product.prodname_actions %} guides](/actions/guides).
|
||||
1. Some starter workflows use secrets. For example, {% raw %}`${{ secrets.npm_token }}`{% endraw %}. If the starter workflow uses a secret, store the value described in the secret name as a secret in your repository. For more information, see "[AUTOTITLE](/actions/security-guides/encrypted-secrets)."
|
||||
1. Optionally, make additional changes. For example, you might want to change the value of `on` to change when the workflow runs.
|
||||
|
||||
@@ -52,15 +52,7 @@ First, enable {% data variables.product.prodname_actions %} for all organization
|
||||
{% data reusables.enterprise-accounts.policies-tab %}
|
||||
{% data reusables.enterprise-accounts.actions-tab %}
|
||||
1. Under "Policies", select **Enable for all organizations**.
|
||||
|
||||
|
||||
1. Select {% data reusables.actions.policy-label-for-select-actions-workflows %} and **Allow actions created by GitHub** to allow local actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %}, and actions created by {% data variables.product.company_short %}.
|
||||
|
||||
{% ifversion actions-workflow-policy %}
|
||||
|
||||
{%- else %}
|
||||
|
||||
{%- endif %}
|
||||
1. To enable local actions{% ifversion actions-workflow-policy %} and reusable workflows, {% endif %} and actions created by {% data variables.product.company_short %}, select {% data reusables.actions.policy-label-for-select-actions-workflows %}, then select **Allow actions created by {% data variables.product.company_short %}**.
|
||||
1. Click **Save**.
|
||||
|
||||
You can configure additional policies to restrict the actions available to {% ifversion ghec or ghae %}enterprise members{% elsif ghes %}users of {% data variables.location.product_location %}{% endif %}. For more information, see "[AUTOTITLE](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#allowing-select-actions-to-run)."
|
||||
|
||||
@@ -22,10 +22,9 @@ When {% data variables.product.prodname_oauth_app %} access restrictions are ena
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.oauth_app_access %}
|
||||
5. Next to the application you'd like to approve, click **Review**.
|
||||
1. Next to the application you'd like to approve, click **Review**.
|
||||
|
||||
6. After you review the information about the requested application, click **Grant access**.
|
||||
|
||||
1. After you review the information about the requested application, click **Grant access**.
|
||||
|
||||
## Further reading
|
||||
|
||||
|
||||
@@ -18,7 +18,7 @@ shortTitle: Deny OAuth App
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.oauth_app_access %}
|
||||
5. Next to the application you'd like to disable, click {% octicon "pencil" aria-label="The edit icon" %}.
|
||||
|
||||
6. Click **Deny access**.
|
||||
|
||||
1. Next to the application you'd like to disable, click {% octicon "pencil" aria-label="Update policy" %}.
|
||||
|
||||
|
||||
1. Click **Deny access**.
|
||||
|
||||
@@ -24,7 +24,5 @@ shortTitle: Disable OAuth App
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.oauth_app_access %}
|
||||
5. Click **Remove restrictions**.
|
||||
|
||||
6. After you review the information about disabling third-party application restrictions, click **Yes, remove application restrictions**.
|
||||
|
||||
1. Click **Remove restrictions**.
|
||||
1. After you review the information about disabling third-party application restrictions, click **Yes, remove application restrictions**.
|
||||
|
||||
@@ -29,7 +29,5 @@ shortTitle: Enable OAuth App
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.oauth_app_access %}
|
||||
5. Under "Third-party application access policy," click **Setup application access restrictions**.
|
||||
|
||||
6. After you review the information about third-party access restrictions, click **Restrict third-party application access**.
|
||||
|
||||
1. Under "Third-party application access policy," click **Setup application access restrictions**.
|
||||
1. After you review the information about third-party access restrictions, click **Restrict third-party application 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 %}
|
||||
|
||||
Enterprises can add their runners to groups for access management. Enterprises can create groups of runners that are accessible to specific organizations in the enterprise account{% ifversion restrict-groups-to-workflows %} or to specific workflows{% endif %}. Organization owners can then assign additional granular repository{% ifversion restrict-groups-to-workflows %} or workflow{% endif %} access policies to the enterprise runner groups. For information about how to create a runner group with the REST API, see the enterprise endpoints in the [{% data variables.product.prodname_actions %} REST API](/rest/actions#self-hosted-runner-groups).
|
||||
@@ -14,15 +14,6 @@ Runners are automatically assigned to the default group when created, and can on
|
||||
When creating a group, you must choose a policy that defines which organizations have access to the runner group.
|
||||
|
||||
{% data reusables.actions.runner-groups-add-to-enterprise-first-steps %}
|
||||
1. To choose a policy for organization access, select the **Organization access** drop-down, and click a policy. You can configure a runner group to be accessible to a specific list of organizations, or all organizations in the enterprise.{% ifversion ghes %} By default, only private repositories can access runners in a runner group, but you can override this.{% endif %}
|
||||
|
||||
{%- ifversion ghec or ghes %}
|
||||
|
||||
|
||||
{%- elsif ghae %}
|
||||
|
||||
|
||||
{%- endif %}
|
||||
1. To choose a policy for organization access, select the **Organization access** dropdown menu and click a policy. You can configure a runner group to be accessible to a specific list of organizations, or all organizations in the enterprise.{% ifversion ghes %} By default, only private repositories can access runners in a runner group, but you can override this.{% endif %}
|
||||
{% data reusables.actions.runner-group-assign-policy-workflow %}
|
||||
1. Click **Save group** to create the group and apply the policy.
|
||||
|
||||
|
||||
@@ -1,7 +1,2 @@
|
||||
1. Under **Fork pull request workflows**, select your options. For example:
|
||||
{% ifversion actions-private-fork-workflow-approvals %}
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
1. Under **Fork pull request workflows**, select your options.
|
||||
1. Click **Save** to apply the settings.
|
||||
|
||||
@@ -1,2 +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,4 +1,2 @@
|
||||
1. Under **Fork pull request workflows from outside collaborators**, select your option. The options are listed from least restrictive to most restrictive.
|
||||
|
||||
|
||||
1. Under **Fork pull request workflows from outside collaborators**, select your option. The options are listed from least restrictive to most restrictive.
|
||||
1. Click **Save** to apply the settings.
|
||||
|
||||
@@ -1,2 +1 @@
|
||||
1. Type the extra information you'd like on your receipt, then click **Save contact information**.
|
||||
|
||||
1. In the text fields, type the extra information you'd like on your receipt, then click **Save contact information**.
|
||||
|
||||
@@ -1,6 +1 @@
|
||||
1. Click **Connect to {% data variables.product.prodname_dotcom_the_website %}**.
|
||||
{% ifversion ghes %}
|
||||
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -1,2 +1 @@
|
||||
1. In the left sidebar, click **{% data variables.product.prodname_github_connect %}**.
|
||||
|
||||
|
||||
@@ -1,2 +1 @@
|
||||
1. Under "Contributions", select **Send my contribution counts to {% data variables.product.prodname_dotcom_the_website %}**, then click **Update contributions.**
|
||||
|
||||
|
||||
@@ -1 +1 @@
|
||||
1. In the "Integrations" section of the sidebar, click **{% octicon "key" aria-label="The key icon" %} Third-party access**.
|
||||
1. In the "Integrations" section of the sidebar, click **{% octicon "apps" aria-hidden="true" %} OAuth application policy**.
|
||||
|
||||
@@ -1,2 +1 @@
|
||||
1. Optionally, to turn off scheduled reminders for pull requests that have already been reviewed and approved, select **Ignore approved pull requests**. Then, click the **Ignore with 1 or more approvals** to choose how many approvals a pull request must have to be ignored.
|
||||
|
||||
1. Optionally, to turn off scheduled reminders for pull requests that have already been reviewed and approved, select **Ignore approved pull requests**. Then, click **Ignore with 1 or more approvals** to choose how many approvals a pull request must have to be ignored.
|
||||
|
||||
@@ -1,2 +1 @@
|
||||
1. Optionally, to send reminders to the pull request authors after the review requests have been fulfilled, select **Remind authors after reviews** and choose the number of reviews required before a reminder is sent.
|
||||
|
||||
|
||||
@@ -1,3 +1,2 @@
|
||||
1. At the bottom of the page, click **Delete this reminder**.
|
||||
|
||||
1. To confirm that you want to delete the scheduled reminder, click **OK**.
|
||||
|
||||
@@ -1,2 +1 @@
|
||||
1. Next to the scheduled reminder you'd like to update, click **Edit**.
|
||||
|
||||
|
||||
@@ -1,2 +1 @@
|
||||
1. Optionally, to exclude draft pull requests from scheduled reminders, select **Ignore drafts**. For more information, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests#draft-pull-requests)."
|
||||
|
||||
1. Optionally, to exclude draft pull requests from scheduled reminders, select **Ignore drafts**. For more information, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests#draft-pull-requests)."
|
||||
@@ -1,2 +1 @@
|
||||
1. Under "Ignored labels", type a comma-separated list of labels. Scheduled reminders won't include any pull requests that have one or more of these labels.
|
||||
|
||||
1. Under "Ignored labels", type a comma-separated list of labels. Scheduled reminders won't include any pull requests that have one or more of these labels.
|
||||
|
||||
@@ -1,2 +1 @@
|
||||
1. Under "Ignored terms", type a comma-separated list of terms that may appear in titles of pull requests. Scheduled reminders won't include any pull requests that contain one or more of these terms in their titles.
|
||||
|
||||
1. Under "Ignored terms", type a comma-separated list of terms that may appear in titles of pull requests. Scheduled reminders won't include any pull requests that contain one or more of these terms in their titles.
|
||||
|
||||
@@ -1,2 +1 @@
|
||||
1. Under "Minimum age", type the age of a pull request, in hours. Scheduled reminders won't include pull requests that are newer than this age limit.
|
||||
|
||||
|
||||
@@ -1,2 +1 @@
|
||||
1. Under "Minimum staleness", type the time since the last activity on a pull request, in hours. Scheduled reminders won't include pull requests whose last activity was more recent than this time.
|
||||
|
||||
|
||||
@@ -1,2 +1 @@
|
||||
1. Optionally, to only include pull requests where a review is specifically requested from the team or a team member, select **Require review requests**. If you don't select this option, all pull requests are included in the scheduled reminder.
|
||||
|
||||
1. Optionally, to only include pull requests where a review is specifically requested from the team or a team member, select **Require review requests**. If you don't select this option, all pull requests are included in the scheduled reminder.
|
||||
|
||||
@@ -1,2 +1 @@
|
||||
1. Under "Required labels", type a comma-separated list of labels. Scheduled reminders will only include pull requests that haven't already been ignored, if they have one or more of these labels.
|
||||
|
||||
1. Under "Required labels", type a comma-separated list of labels. Scheduled reminders will only include pull requests that haven't already been ignored, if they have one or more of these labels.
|
||||
|
||||
@@ -1,2 +1 @@
|
||||
1. Under "Slack channel", type the name of the Slack channel where you'd like to receive notifications.
|
||||
|
||||
|
||||
@@ -1,5 +1,3 @@
|
||||
1. Under "Tracked repositories," choose which repositories you'd like the team to receive pull request review reminders for.
|
||||
- To receive reminders for all repositories that the chosen team has access to, click **All repositories**.
|
||||
1. Under "Tracked repositories," choose which repositories you'd like the team to receive pull request review reminders for.
|
||||
- To receive reminders for all repositories that the chosen team has access to, click **All repositories**.
|
||||
- To receive reminders for a subset of repositories, click **Only select repositories**, then select one or more repositories that the chosen team has access to.
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user