Make some images accessible in the images/help/settings directory (…

…#36528)

Co-authored-by: Isaac Brown <[email protected]>

content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md

@@ -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.
-![View application button](/assets/images/help/settings/settings-third-party-view-app.png)
-4. Next to the organization you'd like the {% data variables.product.prodname_oauth_app %} to access, click **Request access**.
-![Request access button](/assets/images/help/settings/settings-third-party-request-access.png)
-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
 

content/actions/using-workflows/using-starter-workflows.md

@@ -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 %}![Configure this workflow](/assets/images/help/settings/actions-create-starter-workflow-updated-ui.png){% else %}![Set up this workflow](/assets/images/help/settings/actions-create-starter-workflow.png){% 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.

content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md

@@ -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**.
-
-   ![Screenshot of "Enable for all organizations" policy for {% data variables.product.prodname_actions %}](/assets/images/help/settings/actions-policy-enable-for-all-organizations.png)
-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 %}
-   ![Screenshot of "Allow select actions" and "Allow actions created by {% data variables.product.company_short %}" for {% data variables.product.prodname_actions %}](/assets/images/help/settings/actions-policy-allow-select-actions-and-actions-from-github-with-workflows.png)
-   {%- else %}
-   ![Screenshot of "Allow select actions" and "Allow actions created by {% data variables.product.company_short %}" for {% data variables.product.prodname_actions %}](/assets/images/help/settings/actions-policy-allow-select-actions-and-actions-from-github.png)
-   {%- 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)."

content/organizations/managing-oauth-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md

@@ -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**.
 ![Review request link](/assets/images/help/settings/settings-third-party-approve-review.png)
-6. After you review the information about the requested application, click **Grant access**.
-![Grant access button](/assets/images/help/settings/settings-third-party-approve-grant.png)
+1. After you review the information about the requested application, click **Grant access**.
 
 ## Further reading
 

content/organizations/managing-oauth-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md

@@ -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" %}.
-  ![Edit icon](/assets/images/help/settings/settings-third-party-deny-edit.png)
-6. Click **Deny access**.
-  ![Deny confirmation button](/assets/images/help/settings/settings-third-party-deny-confirm.png)
+1. Next to the application you'd like to disable, click {% octicon "pencil" aria-label="Update policy" %}.
+
+   ![Screenshot of the "Third-party application access policy" page. To the right of an approved application, a pencil icon is outlined in dark orange.](/assets/images/help/settings/settings-third-party-deny-edit.png)
+1. Click **Deny access**.

content/organizations/managing-oauth-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md

@@ -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**.
-  ![Remove restrictions button](/assets/images/help/settings/settings-third-party-remove-restrictions.png)
-6. After you review the information about disabling third-party application restrictions, click **Yes, remove application restrictions**.
-  ![Remove confirmation button](/assets/images/help/settings/settings-third-party-confirm-disable.png)
+1. Click **Remove restrictions**.
+1. After you review the information about disabling third-party application restrictions, click **Yes, remove application restrictions**.

content/organizations/managing-oauth-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md

@@ -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**.
-  ![Set up restrictions button](/assets/images/help/settings/settings-third-party-set-up-restrictions.png)
-6. After you review the information about third-party access restrictions, click **Restrict third-party application access**.
-  ![Restriction confirmation button](/assets/images/help/settings/settings-third-party-restrict-confirm.png)
+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**.

data/reusables/actions/creating-a-runner-group-for-an-enterprise.md

@@ -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 %}
-
-   ![Add runner group options](/assets/images/help/settings/actions-enterprise-account-add-runner-group-options.png)
-   {%- elsif ghae %}
-
-   ![Add runner group options](/assets/images/help/settings/actions-enterprise-account-add-runner-group-options-ae.png)
-   {%- 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.
-

data/reusables/actions/private-repository-forks-configure.md

@@ -1,7 +1,2 @@
-1. Under **Fork pull request workflows**, select your options. For example:
-  {% ifversion actions-private-fork-workflow-approvals %}
-   ![Enable, disable, or limits actions for this repository](/assets/images/help/settings/actions-fork-pull-request-workflows-require-approval.png){% else %}
-
-   ![Enable, disable, or limits actions for this repository](/assets/images/help/settings/actions-fork-pull-request-workflows.png){% endif %}
-
+1. Under **Fork pull request workflows**, select your options.
 1. Click **Save** to apply the settings.

data/reusables/actions/workflows-from-public-fork-setting.md

@@ -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. 
-
-   ![Setting for approval for workflows from public forks](/assets/images/help/settings/actions-fork-pull-request-approval.png)
+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.

data/reusables/dotcom_billing/extra_info_receipt.md

@@ -1,2 +1 @@
-1. Type the extra information you'd like on your receipt, then click **Save contact information**.
- ![Contact info field](/assets/images/help/settings/Billing-extra-info-field.png)
+1. In the text fields, type the extra information you'd like on your receipt, then click **Save contact information**.

data/reusables/github-connect/connect-dotcom-and-enterprise.md

@@ -1,6 +1 @@
 1. Click **Connect to {% data variables.product.prodname_dotcom_the_website %}**.
-{% ifversion ghes %}
-   ![Connect to GitHub.com from GitHub Enterprise Server settings](/assets/images/help/settings/github.com_end_user_connection.png)
-{% else %}
-   ![Connect to GitHub.com from GitHub AE settings](/assets/images/enterprise/github-ae/settings/github.com-end-user-connection.png)
-{% endif %}

data/reusables/github-connect/github-connect-tab-user-settings.md

@@ -1,2 +1 @@
 1. In the left sidebar, click **{% data variables.product.prodname_github_connect %}**.
-   ![GitHub Connect tab in the user settings sidebar](/assets/images/help/settings/github-connect-tab-user-settings.png)

data/reusables/github-connect/send-contribution-counts-to-githubcom.md

@@ -1,2 +1 @@
 1. Under "Contributions", select **Send my contribution counts to {% data variables.product.prodname_dotcom_the_website %}**, then click **Update contributions.**
-   ![Send contributions checkbox and update contributions button](/assets/images/help/settings/send-and-update-contributions.png)

data/reusables/organizations/oauth_app_access.md

@@ -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**.

data/reusables/reminders/approved-prs.md

@@ -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.
-![Ignore approved pull requests checkbox](/assets/images/help/settings/scheduled-reminders-ignore-approved-prs.png)
+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.

data/reusables/reminders/author-reviews.md

@@ -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.
-![Remind authors after reviews checkbox](/assets/images/help/settings/scheduled-reminders-remind-authors.png)

data/reusables/reminders/delete.md

@@ -1,3 +1,2 @@
 1. At the bottom of the page, click **Delete this reminder**.
-![Delete a scheduled reminder button](/assets/images/help/settings/scheduled-reminders-delete.png)
 1. To confirm that you want to delete the scheduled reminder, click **OK**.

data/reusables/reminders/edit-existing.md

@@ -1,2 +1 @@
 1. Next to the scheduled reminder you'd like to update, click **Edit**.
-![Edit existing scheduled reminder](/assets/images/help/settings/scheduled-reminders-edit-existing.png)

data/reusables/reminders/ignore-drafts.md

@@ -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)."
-![Ignore draft pull requests checkbox](/assets/images/help/settings/scheduled-reminders-ignore-drafts.png)
+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)."

data/reusables/reminders/ignored-labels.md

@@ -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. 
-![Ignored labels field](/assets/images/help/settings/scheduled-reminders-ignored-labels-field.png)
+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.

data/reusables/reminders/ignored-terms.md

@@ -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. 
-![Ignored terms field](/assets/images/help/settings/scheduled-reminders-ignored-terms-field.png)
+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.

data/reusables/reminders/min-age.md

@@ -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.
-![Ignored labels field](/assets/images/help/settings/scheduled-reminders-min-age-field.png)

data/reusables/reminders/min-staleness.md

@@ -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.
-![Minimum staleness field](/assets/images/help/settings/scheduled-reminders-min-staleness-field.png)

data/reusables/reminders/no-review-requests.md

@@ -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. 
-![Ignore pull requests with no review requests checkbox](/assets/images/help/settings/scheduled-reminders-prs-without-requests.png)
+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.

data/reusables/reminders/required-labels.md

@@ -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. 
-![Required labels field](/assets/images/help/settings/scheduled-reminders-required-labels-field.png)
+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.

data/reusables/reminders/slack-channel.md

@@ -1,2 +1 @@
 1. Under "Slack channel", type the name of the Slack channel where you'd like to receive notifications.
-![Slack channel field](/assets/images/help/settings/scheduled-reminders-slack-channel.png)

data/reusables/reminders/tracked-repos.md

@@ -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.
-
-  ![Choose tracked repositories](/assets/images/help/settings/scheduled-reminders-tracked-repos.png)