Make some more images in the images/help/repository directory (D-O) accessible (4/4) (#35911)

Co-authored-by: Sophie <29382425+sophietheking@users.noreply.github.com>

content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/troubleshooting-commits-on-your-timeline.md

@@ -26,8 +26,6 @@ In the "Contribution activity" section of your profile page, you can click the n
 
 If you click a commit link from your profile page and don't see all of the expected commits on the repository's commits page, then it's possible the commit history in Git was rewritten and the commit author date and the commit date are different.
 
-![Repository page with message that says "no commits found for octocat"](/assets/images/help/repository/no-commits-found.png)
-
 ## How GitHub uses the Git author date and commit date
 
 In Git, the author date is when someone first creates a commit with `git commit`. The commit date is identical to the author date unless someone changes the commit date by using `git commit --amend`, a force push, a rebase, or other Git commands.

content/actions/creating-actions/publishing-actions-in-github-marketplace.md

@@ -39,20 +39,15 @@ To draft a new release and publish the action to {% data variables.product.prodn
 
 {% data reusables.repositories.navigate-to-repo %}
 1. Navigate to the action metadata file in your repository (`action.yml` or `action.yaml`), and you'll see a banner to publish the action to {% data variables.product.prodname_marketplace %}. Click **Draft a release**.
+1. Under "Release Action", select **Publish this Action to the {% data variables.product.prodname_marketplace %}**.
 
-   ![Publish this action to marketplace button](/assets/images/help/repository/publish-github-action-to-marketplace-button.png)
-1. Under "Release Action", select the checkbox to publish the action to the {% data variables.product.prodname_marketplace %}. If you can't select the checkbox, you must first click the link to read and accept the {% data variables.product.prodname_marketplace %} Developer Agreement.
-![Select publish to Marketplace](/assets/images/help/repository/marketplace_actions_publish.png)
-1. If the labels in your metadata file contain any problems, you will see an error message.
-![See notification](/assets/images/help/repository/marketplace_actions_fixerrors.png)
-1. If you see any on-screen suggestions, address them by updating your metadata file. Once complete, you will see an "Everything looks good!" message.
-![Fix errors](/assets/images/help/repository/marketplace_actions_looksgood.png)
-1. Choose a "Primary Category" and, optionally, "Another Category" which will help people find your action in {% data variables.product.prodname_marketplace %}.
-![Choose category](/assets/images/help/repository/marketplace_actions_categories.png)
-1. Tag your Action with a version, and add a release title. This helps people know what changes or features the release includes. People will see the version in the action's dedicated {% data variables.product.prodname_marketplace %} page.
-![Tag a version](/assets/images/help/repository/marketplace_actions_version.png)
+   If you can't select the checkbox, you must first click the link to read and accept the {% data variables.product.prodname_marketplace %} Developer Agreement.
+1. If the labels in your metadata file contain any problems, you will see an error message. Address them by updating your metadata file. Once complete, you will see an "Everything looks good!" message.
+1. Select the **Primary Category** dropdown menu and click a category that will help people find your action in {% data variables.product.prodname_marketplace %}.
+1. Optionally, select the **Another Category** dropdown menu and click a secondary category.
+1. In the tag field, type a version for your action. This helps people know what changes or features the release includes. People will see the version in the action's dedicated {% data variables.product.prodname_marketplace %} page.
+1. In the title field, type a release title.
 1. Complete all other fields and click **Publish release**. Publishing requires you to use two-factor authentication. For more information, see "[AUTOTITLE](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)."
-![Publish the release](/assets/images/help/repository/marketplace_actions_publishrelease.png)
 
 ## Removing an action from {% data variables.product.prodname_marketplace %}
 

content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md

@@ -32,15 +32,17 @@ Users in India can contact GitHub's Grievance Officer for India [here](https://s
 ## Reporting an issue or pull request
 
 1. Navigate to the issue or pull request you'd like to report.
-1. In the upper-right corner of the issue or pull request, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %}, then click **Report content**.
-  ![Button to report a comment](/assets/images/help/repository/menu-report-issue-or-pr.png)
+1. In the upper-right corner of the issue or pull request, click {% octicon "kebab-horizontal" aria-label="Show options" %}, then click **Report content**.
+
+   ![Screenshot of an issue description. In the header, a kebab icon is outlined in dark orange.](/assets/images/help/repository/menu-report-issue-or-pr.png)
 {% data reusables.community.report-content %}
 
 ## Reporting a comment
 
 1. Navigate to the comment you'd like to report.
-1. In the upper-right corner of the comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %}, then click **Report content**.
-![Kebab menu with option to report a comment](/assets/images/help/repository/menu-report-comment.png)
+1. In the upper-right corner of the comment, click {% octicon "kebab-horizontal" aria-label="Show options" %}, then click **Report content**.
+
+   ![Screenshot of a comment. In the header, a kebab icon is outlined in dark orange.](/assets/images/help/repository/menu-report-issue-or-pr.png)
 {% data reusables.community.report-content %}
 
 ## Reporting an app in {% data variables.product.prodname_marketplace %}
@@ -65,6 +67,5 @@ Users in India can contact GitHub's Grievance Officer for India [here](https://s
 - "[AUTOTITLE](/communities/setting-up-your-project-for-healthy-contributions)"
 - "[AUTOTITLE](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)"
 - "[AUTOTITLE](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"{% ifversion fpt or ghec %}
-- "[AUTOTITLE](/communities/maintaining-your-safety-on-github)"
 - "[AUTOTITLE](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)"{% endif %}
 - "[AUTOTITLE](/communities/moderating-comments-and-conversations/tracking-changes-in-a-comment)"

content/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project.md

@@ -49,7 +49,6 @@ If the code of conduct you want to use isn't available in the provided templates
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.files.add-file %}
 3. In the file name field, type the name and extension for the file.
-  ![New code of conduct file name](/assets/images/help/repository/new-code-of-conduct-file-name.png)
     - To make your code of conduct visible in the repository's root directory, type *CODE_OF_CONDUCT* in the file name field.
     - To make your code of conduct visible in the repository's `docs` directory, type *docs/CODE_OF_CONDUCT*.
     - To make your code of conduct visible in the repository's `.github` directory, type *.github/CODE_OF_CONDUCT*.

content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md

@@ -40,7 +40,6 @@ You can create default contribution guidelines for your organization{% ifversion
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.files.add-file %}
 3. Decide whether to store your contributing guidelines in your repository's root, `docs`, or `.github` directory. Then, in the filename field, type the name and extension for the file. Contributing guidelines filenames are not case sensitive. Files are rendered in rich text format if the file extension is in a supported format. For more information, see "[AUTOTITLE](/repositories/working-with-files/using-files/working-with-non-code-files#rendering-differences-in-prose-documents)."
-  ![New file name](/assets/images/help/repository/new-file-name.png)
     - To make your contributing guidelines visible in the repository's root directory, type *CONTRIBUTING*.
     - To make your contributing guidelines visible in the repository's `docs` directory, type *docs/* to create the new directory, then *CONTRIBUTING*.
     - If a repository contains more than one *CONTRIBUTING* file, then the file shown in links is chosen from locations in the following order: the `.github` directory, then the repository's root directory, and finally the `docs` directory.

content/issues/tracking-your-work-with-issues/creating-an-issue.md

@@ -90,10 +90,11 @@ You can open a new issue from a specific line or lines of code in a file or pull
 {% data reusables.repositories.navigate-to-repo %}
 1. Locate the code you want to reference in an issue:
     - To open an issue about code in a file, navigate to the file.
-    - To open an issue about code in a pull request, navigate to the pull request and click {% octicon "diff" aria-label="The file diff icon" %} **Files changed**. Then, browse to the file that contains the code you want included in your comment, and click **View**.
+    - To open an issue about code in a pull request, navigate to the pull request and click {% octicon "diff" aria-hidden="true" %} **Files changed**. Then, browse to the file that contains the code you want included in your comment, and click **View**.
 {% data reusables.repositories.choose-line-or-range %}
-4. To the left of the code range, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %}. In the drop-down menu, click **Reference in new issue**.
-  ![Kebab menu with option to open a new issue from a selected line](/assets/images/help/repository/open-new-issue-specific-line.png)
+1. To the left of the code range, click {% octicon "kebab-horizontal" aria-label="Code line X options" %}. In the dropdown menu, click **Reference in new issue**.
+
+   ![Screenshot of a file, with 8 lines selected. To the left of the first selected line, a button labeled with a kebab icon is outlined in dark orange.](/assets/images/help/repository/open-new-issue-specific-line.png)
 {% data reusables.repositories.type-issue-title-and-description %}
 {% data reusables.repositories.assign-an-issue-as-project-maintainer %}
 {% data reusables.repositories.submit-new-issue %}

content/issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests.md

@@ -23,7 +23,6 @@ type: how_to
 {% data reusables.project-management.milestones %}
 4. Choose one of these options:
     - To create a new milestone, click **New Milestone**.
-  ![New milestone button](/assets/images/help/repository/new-milestone.png)
     - To edit a milestone, next to the milestone you want to edit, click **Edit**.
 
        ![Screenshot of the list of milestones. Within the entry for the "beta release" milestone, a link, labeled "Edit," is outlined in dark orange.](/assets/images/help/repository/edit-milestone.png)

content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md

@@ -53,8 +53,9 @@ When you create a branch rule, the branch you specify doesn't have to exist yet
 1. Optionally, enable required pull requests.
    - Under "Protect matching branches", select **Require a pull request before merging**.
      ![Pull request review restriction checkbox](/assets/images/help/repository/PR-reviews-required-updated.png)
-   - Optionally, to require approvals before a pull request can be merged, select **Require approvals**, click the **Required number of approvals before merging** drop-down menu, then select the number of approving reviews you would like to require on the branch.
-     ![Drop-down menu to select number of required review approvals](/assets/images/help/repository/number-of-required-review-approvals-updated.png)
+   - Optionally, to require approvals before a pull request can be merged, select **Require approvals**.
+
+      Select the **Required number of approvals before merging** dropdown menu, then click the number of approving reviews you would like to require on the branch.
    - Optionally, to dismiss a pull request approval review when a code-modifying commit is pushed to the branch, select **Dismiss stale pull request approvals when new commits are pushed**.
      ![Dismiss stale pull request approvals when new commits are pushed checkbox](/assets/images/help/repository/PR-reviews-required-dismiss-stale.png)
    - Optionally, to require review from a code owner when the pull request affects code that has a designated owner, select **Require review from Code Owners**. For more information, see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners)."

content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md

@@ -20,7 +20,7 @@ shortTitle: Classify with topics
 
 With topics, you can explore repositories in a particular subject area, find projects to contribute to, and discover new solutions to a specific problem. Topics appear on the main page of a repository. You can click a topic name to {% ifversion fpt or ghec %}see related topics and a list of other repositories classified with that topic{% else %}search for other repositories with that topic{% endif %}.
 
-![Main page of the test repository showing topics](/assets/images/help/repository/os-repo-with-topics.png)
+![Screenshot of the github/docs repository. In the right sidebar, three topics are outlined in dark orange: "docs," "hacktoberfest," and "works-with-codespaces."](/assets/images/help/repository/os-repo-with-topics.png)
 
 To browse the most used topics, go to https://github.com/topics/.
 

content/repositories/working-with-files/managing-files/creating-new-files.md

@@ -21,14 +21,13 @@ When creating a file on {% data variables.product.product_name %}, consider the
 {% data reusables.repositories.sensitive-info-warning %}
 
 {% data reusables.repositories.navigate-to-repo %}
-2. In your repository, browse to the folder where you want to create a file.
+1. In your repository, browse to the folder where you want to create a file.
 {% data reusables.files.add-file %}
-4. In the file name field, type the name and extension for the file. To create subdirectories, type the `/` directory separator.
-![New file name](/assets/images/help/repository/new-file-name.png)
-5. On the **Edit new file** tab, add content to the file.
-![Content in new file](/assets/images/help/repository/new-file-content.png)
-6. To review the new content, click **Preview**.
-![New file preview button](/assets/images/help/repository/new-file-preview.png)
+1. In the file name field, type the name and extension for the file. To create subdirectories, type the `/` directory separator.
+1. In the file contents text box, type content for the file.
+1. To review the new content, above the file contents, click **Preview**.
+
+   ![Screenshot of a file in edit mode. Above the text box for editing file contents, a tab, labeled "Preview", outlined in dark orange.](/assets/images/help/repository/new-file-preview.png)
 {% data reusables.files.write_commit_message %}
 {% data reusables.files.choose-commit-email %}
 {% data reusables.files.choose_commit_branch %}

content/repositories/working-with-files/managing-files/moving-a-file-to-a-new-location.md

@@ -32,10 +32,10 @@ In addition to changing the file location, you can also [update the contents of
 {% endtip %}
 
 1. In your repository, browse to the file you want to move.
-2. In the upper right corner of the file view, click {% octicon "pencil" aria-label="The edit icon" %} to open the file editor.
-![Edit file icon](/assets/images/help/repository/move-file-edit-file-icon.png)
-3. In the filename field, change the name of the file using these guidelines:
-  ![Editing a file name](/assets/images/help/repository/moving_files.gif)
+1. In the upper right corner of the file view, click {% octicon "pencil" aria-label="Edit file" %} to open the file editor.
+
+   ![Screenshot of a file. In the header, a button, labeled with a pencil icon, is outlined in dark orange.](/assets/images/help/repository/edit-file-edit-button.png)
+1. In the filename field, change the name of the file using these guidelines:
     - To move the file **into a subfolder**, type the name of the folder you want, followed by `/`. Your new folder name becomes a new item in the navigation breadcrumbs.
     - To move the file into a directory **above the file's current location**, place your cursor at the beginning of the filename field, then either type `../` to jump up one full directory level, or type the `backspace` key to edit the parent folder's name.
 {% data reusables.files.write_commit_message %}

content/repositories/working-with-files/using-files/working-with-non-code-files.md

@@ -359,7 +359,8 @@ graph TD
 ```
 
 When you view the file in the repository, it is rendered as a flow chart.
-![Rendered mermaid file diagram](/assets/images/help/repository/mermaid-file-diagram.png)
+
+![Screenshot of a flow chart. Two arrows point from a box labeled "A" to boxes labeled "B" and "C," and two more arrows point from "B" and "C" to "D."](/assets/images/help/repository/mermaid-file-diagram.png)
 
 ### Troubleshooting Mermaid files
 

data/reusables/files/propose_new_file.md

@@ -1,2 +1 @@
 1. Click **Propose new file.**
-![Propose new file button](/assets/images/help/repository/new-file-commit-button.png)