1
0
mirror of synced 2025-12-19 18:10:59 -05:00

Hack week 2025: Second batch of alt text fixes for the data/reusables folder (#53955)

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Ben Ahmady <32935794+subatoi@users.noreply.github.com>
This commit is contained in:
Felicity Chapman
2025-01-16 17:18:45 +00:00
committed by GitHub
parent 9d03e0157e
commit 31486e7747
17 changed files with 19 additions and 19 deletions

View File

@@ -1,3 +1,3 @@
1. Next to the search field, click **Milestones**. 1. Next to the search field, click **Milestones**.
![Screenshot of the list of issues for a repository. Above the list, a button, labeled with a signpost icon and "Milestones," is outlined in dark orange.](/assets/images/help/issues/issues-milestone-button.png) ![Screenshot of the list of issues for a repository. Above the list, a button, labeled with a signpost icon and "Milestones," is outlined in orange.](/assets/images/help/issues/issues-milestone-button.png)

View File

@@ -1,2 +1,2 @@
1. Under "Times", click **9:00 AM** {% octicon "triangle-down" aria-label="The down triangle icon" %} to select one or more times you'd like to receive scheduled reminders. Optionally, to change your timezone, click {% octicon "triangle-down" aria-label="The down triangle icon" %} next to your current timezone and select a different time zone. 1. Under "Times", click **9:00 AM** {% octicon "triangle-down" aria-label="The down triangle icon" %} to select one or more times you'd like to receive scheduled reminders. Optionally, to change your timezone, click {% octicon "triangle-down" aria-label="The down triangle icon" %} next to your current timezone and select a different time zone.
![Screenshot of Scheduled reminder settings showing drop-down menus to select hours and the associated time zone for reminders in Slack. The hours menu is open, with checkmarks next to 9:00 AM and 10:00 AM.](/assets/images/help/settings/scheduled-reminders-times.png) ![Screenshot of Scheduled reminder options used to select the hour and time zone for reminders. 9:00 AM and 10:00 AM are checked in the open hours menu.](/assets/images/help/settings/scheduled-reminders-times.png)

View File

@@ -6,4 +6,4 @@ On the "Rule Insights" page, you will see a timeline of the following user actio
If a ruleset is running in "Evaluate" mode, you can see actions that would have passed or failed if the ruleset had been active. If a ruleset is running in "Evaluate" mode, you can see actions that would have passed or failed if the ruleset had been active.
![Screenshot of the "Rule Insights" page. Three actions are listed: one marked "pass," one marked "bypass," and one marked "fail" with an "evaluate" label.](/assets/images/help/repository/rule-insights.png) ![Screenshot of the "Rule Insights" page. Three actions are listed marked: "Pass," "Bypass," and "Fail". The failed action has with an "evaluate" label.](/assets/images/help/repository/rule-insights.png)

View File

@@ -1,3 +1,3 @@
1. Under your repository name, click **{% octicon "graph" aria-hidden="true" %} Insights**. 1. Under your repository name, click **{% octicon "graph" aria-hidden="true" %} Insights**.
![Screenshot of the main page of a repository. In the horizontal navigation bar, a tab, labeled with a graph icon and "Insights," is outlined in dark orange.](/assets/images/help/repository/repo-nav-insights-tab.png) ![Screenshot of the main page of a repository. In the horizontal navigation bar, a tab, labeled with a graph icon and "Insights," is outlined in orange.](/assets/images/help/repository/repo-nav-insights-tab.png)

View File

@@ -1,3 +1,3 @@
A status badge shows whether a workflow is currently failing or passing. A common place to add a status badge is in the `README.md` file of your repository, but you can add it to any web page you'd like. By default, badges display the status of your default branch. If there are no workflow runs on your default branch, it will display the status of the most recent run across all branches. You can display the status of a workflow run for a specific branch or event using the `branch` and `event` query parameters in the URL. A status badge shows whether a workflow is currently failing or passing. A common place to add a status badge is in the `README.md` file of your repository, but you can add it to any web page you'd like. By default, badges display the status of your default branch. If there are no workflow runs on your default branch, it will display the status of the most recent run across all branches. You can display the status of a workflow run for a specific branch or event using the `branch` and `event` query parameters in the URL.
![Screenshot of a workflow status badge. The left side contains the octocat logo and "GitHub Actions Demo", the name of the workflow. The right half is green with the text "passing."](/assets/images/help/repository/actions-workflow-status-badge.png) ![Screenshot of a workflow status badge. From right to left it shows: the GitHub logo, workflow name ("GitHub Actions Demo"), and status ("passing").](/assets/images/help/repository/actions-workflow-status-badge.png)

View File

@@ -6,5 +6,5 @@
* To create a ruleset targeting branches, click **New branch ruleset**. * To create a ruleset targeting branches, click **New branch ruleset**.
* To create a ruleset targeting tags, select {% octicon "triangle-down" aria-label="Open ruleset creation menu" %}, then click **New tag ruleset**. * To create a ruleset targeting tags, select {% octicon "triangle-down" aria-label="Open ruleset creation menu" %}, then click **New tag ruleset**.
![Screenshot of the "Rulesets" page. Next to the "New branch ruleset" button, a dropdown menu is expanded, with an option labeled "New tag ruleset" outlined in orange.](/assets/images/help/repository/new-tag-ruleset.png) ![Screenshot of the "Rulesets" page showing the "New branch ruleset" dropdown menu expanded. The "New tag ruleset" option is outlined in orange.](/assets/images/help/repository/new-tag-ruleset.png)
{% endif %} {% endif %}

View File

@@ -2,11 +2,11 @@ When viewing a Markdown file, you can click {% ifversion code-view-ui %}**Code**
{% ifversion code-view-ui %} {% ifversion code-view-ui %}
![Screenshot of a Markdown file in a {% data variables.product.prodname_dotcom %} repository showing options for interacting with the file. A button, labeled "Code", is outlined in dark orange.](/assets/images/help/writing/display-markdown-as-source-global-nav-update.png) ![Screenshot of a Markdown file in a repository showing options for interacting with the file. A button, labeled "Code", is outlined in dark orange.](/assets/images/help/writing/display-markdown-as-source-global-nav-update.png)
{% else %} {% else %}
![Screenshot of a Markdown file in a {% data variables.product.prodname_dotcom %} repository showing options for interacting with the file. The button to display the source blob is outlined in dark orange.](/assets/images/help/writing/display-markdown-as-source.png) ![Screenshot of a Markdown file in a repository showing options for interacting with the file. The icon to display the code is outlined in orange.](/assets/images/help/writing/display-markdown-as-source.png)
{% endif %} {% endif %}

View File

@@ -1,6 +1,6 @@
1. Select the **New ruleset** dropdown, then click **Import a ruleset**. 1. Select the **New ruleset** dropdown, then click **Import a ruleset**.
![Screenshot of the page for repository rulesets. A dropdown menu labeled "New ruleset" is expanded and the "Import a ruleset" option is highlighted with an orange outline.](/assets/images/help/repository/import-a-ruleset.png) ![Screenshot of the page for repository rulesets. The "New ruleset" dropdown menu is expanded and the "Import a ruleset" option is outlined in orange.](/assets/images/help/repository/import-a-ruleset.png)
1. Open the exported JSON file. 1. Open the exported JSON file.
1. Review the imported ruleset and click **Create**. 1. Review the imported ruleset and click **Create**.

View File

@@ -1,3 +1,3 @@
1. To see a list of closed pull requests, click **Closed**. 1. To see a list of closed pull requests, click **Closed**.
![Screenshot of the "Pull requests" page for a repository. A filter, labeled with a checkmark icon and "31 closed", is highlighted with an orange outline.](/assets/images/help/branches/branches-closed.png) ![Screenshot of the "Pull requests" page for a repository. The "Closed" filter shows a checkmark icon and "31 closed". It is outlined in orange.](/assets/images/help/branches/branches-closed.png)

View File

@@ -1,3 +1,3 @@
1. Type a name for your repository, and an optional description. 1. Type a name for your repository, and an optional description.
![Screenshot of a the first step in creating a {% data variables.product.prodname_dotcom %} repository. The "Repository name" field contains the text "hello-world" and is outlined in dark orange.](/assets/images/help/repository/create-repository-name.png) ![Screenshot of a the first step in creating a repository. The "Repository name" field contains the text "hello-world" and is outlined in orange.](/assets/images/help/repository/create-repository-name.png)

View File

@@ -2,4 +2,4 @@
To return to the source diff view, click the **{% octicon "code" aria-label="Display the source diff" %}** button. To return to the source diff view, click the **{% octicon "code" aria-label="Display the source diff" %}** button.
![Screenshot of the "Files changed" tab of a pull request. The button to display the source diff, which is labeled with a code icon, is outlined in dark orange.](/assets/images/help/pull_requests/dependency-review-source-diff.png) ![Screenshot of the "Files changed" tab of a pull request. The button to display the source diff, shown with a code icon, is outlined in orange.](/assets/images/help/pull_requests/dependency-review-source-diff.png)

View File

@@ -1,3 +1,3 @@
1. To see which specific rules failed or required a bypass, click {% octicon "kebab-horizontal" aria-label="View rule runs" %}, then expand the name of the ruleset. 1. To see which specific rules failed or required a bypass, click {% octicon "kebab-horizontal" aria-label="View rule runs" %}, then expand the name of the ruleset.
![Screenshot of the "Rule Insights" page. To the right of an event labeled "octocat created not-allowed," an icon of three horizontal dots is outlined in orange.](/assets/images/help/repository/view-rule-runs.png) ![Screenshot of the "Rule Insights" page. To the right of an event labeled "not-allowed," an icon of three horizontal dots is outlined in orange.](/assets/images/help/repository/view-rule-runs.png)

View File

@@ -2,10 +2,10 @@
{% ifversion global-nav-update %} {% ifversion global-nav-update %}
![Screenshot of the main page of a repository. In the horizontal navigation bar, two tabs, labeled "Issues" and "Pull requests," are each outlined in dark orange.](/assets/images/help/repository/repo-settings-issues-pull-requests-global-nav-update.png) ![Screenshot of the main page of a repository. In the horizontal navigation bar, the "Issues" and "Pull requests" tabs are outlined in orange.](/assets/images/help/repository/repo-settings-issues-pull-requests-global-nav-update.png)
{% else %} {% else %}
![Screenshot of the main page of a repository. In the horizontal navigation bar, two tabs, labeled "Issues" and "Pull requests," are each outlined in dark orange.](/assets/images/help/repository/repo-settings-issues-pull-requests.png) ![Screenshot of the main page of a repository. In the horizontal navigation bar, the "Issues" and "Pull requests" tabs are outlined in orange.](/assets/images/help/repository/repo-settings-issues-pull-requests.png)
{% endif %} {% endif %}

View File

@@ -1,3 +1,3 @@
1. To comment directly on a file, to the right of the file, click {% octicon "comment" aria-label="The comment icon" %} and type your comment. 1. To comment directly on a file, to the right of the file, click {% octicon "comment" aria-label="The comment icon" %} and type your comment.
![Screenshot of an image file on the "Files changed" page of a pull request. To the right of the image file, a comment icon is highlighted with an orange outline.](/assets/images/help/pull_requests/pull-request-comment-on-file.png) ![Screenshot of an image file on the "Files changed" page of a pull request. To the right of the file, a comment icon is outlined in orange.](/assets/images/help/pull_requests/pull-request-comment-on-file.png)

View File

@@ -1,3 +1,3 @@
1. In "Two-factor methods", find the method you want to modify. Next to that method, click **Edit**. If you have multiple methods configured, select {% octicon "kebab-horizontal" aria-label="Manage METHOD" %}, then click **Edit**. 1. In "Two-factor methods", find the method you want to modify. Next to that method, click **Edit**. If you have multiple methods configured, select {% octicon "kebab-horizontal" aria-label="Manage METHOD" %}, then click **Edit**.
![Screenshot of the "Two-factor methods" settings. To the right of "Authenticator app," a dropdown menu, labeled with a kebab icon, is expanded and outlined in orange.](/assets/images/help/2fa/edit-2fa-method-dropdown.png) ![Screenshot of the "Two-factor methods" settings. To the right of "Authenticator app," the kebab icon, is expanded and outlined in orange.](/assets/images/help/2fa/edit-2fa-method-dropdown.png)

View File

@@ -1,3 +1,3 @@
1. Under "Repositories", click **Deleted repositories**. 1. Under "Repositories", click **Deleted repositories**.
![Screenshot of the "Repositories" settings page. Above a list of repositories, a link in gray text, labeled "Deleted repositories," is outlined in orange.](/assets/images/help/settings/deleted-repos.png) ![Screenshot of the "Repositories" settings page. Above a list of repositories, a gray "Deleted repositories" link is outlined in orange.](/assets/images/help/settings/deleted-repos.png)

View File

@@ -1,3 +1,3 @@
1. Next to the repository you want to restore, click **Restore**. 1. Next to the repository you want to restore, click **Restore**.
![Screenshot of a list entry for the "octocat/hello-world" repository. To the right of a repository's name, a button, labeled "Restore," is outlined in orange.](/assets/images/help/settings/restore-button.png) ![Screenshot of a list entry for the "octocat/hello-world" repository. To the right of a repository's name, the "Restore" button is outlined in orange.](/assets/images/help/settings/restore-button.png)