Make some images in the `images/help/repository` directory (D-O) accessible (#35827)

content/actions/creating-actions/creating-a-docker-container-action.md

@@ -251,7 +251,6 @@ jobs:
         run: echo "The time was {% raw %}${{ steps.hello.outputs.time }}"{% endraw %}
 ```
 
-From your repository, click the **Actions** tab, and select the latest workflow run. Under **Jobs** or in the visualization graph, click **A job to say hello**. You should see "Hello Mona the Octocat" or the name you used for the `who-to-greet` input and the timestamp printed in the log.
-
-![A screenshot of using your action in a workflow](/assets/images/help/repository/docker-action-workflow-run-updated.png)
+From your repository, click the **Actions** tab, and select the latest workflow run. Under **Jobs** or in the visualization graph, click **A job to say hello**.
 
+Click **Hello world action step**, and you should see "Hello Mona the Octocat" or the name you used for the `who-to-greet` input printed in the log. Click **Get the output time** to see the timestamp.

content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md

@@ -59,10 +59,10 @@ You can download the log files from your workflow run. You can also download a w
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
 {% data reusables.repositories.navigate-to-job %}
-1. In the upper right corner, click {% octicon "gear" aria-label="The gear icon" %} and select **Download log archive**.
-  
-  ![Download logs drop-down menu](/assets/images/help/repository/download-logs-drop-down-updated-2.png)
-  
+1. In the upper right corner of the log, select the {% octicon "gear" aria-label="Show options" %} dropdown menu, then click **Download log archive**.
+
+  ![Screenshot of the log for a job. In the header, a gear icon is outlined in dark orange.](/assets/images/help/actions/download-logs-drop-down.png)
+
 
   {% ifversion re-run-jobs %}
 
@@ -82,14 +82,12 @@ You can delete the log files from your workflow run. {% data reusables.repositor
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
-1. In the upper right corner, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
-    
+1. In the upper right corner, click {% octicon "kebab-horizontal" aria-label="Show options" %}.
+
     ![Kebab-horizontal icon](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated-2.png)
-    
-2. To delete the log files, click the **Delete all logs** button and review the confirmation prompt. 
-  
-  ![Delete all logs](/assets/images/help/repository/delete-all-logs-updated-2.png)
-  
+
+2. To delete the log files, click the **Delete all logs** button and review the confirmation prompt.
+
 After deleting logs, the **Delete all logs** button is removed to indicate that no log files remain in the workflow run.
 
 ## Viewing logs with {% data variables.product.prodname_cli %}

content/get-started/privacy-on-github/requesting-an-archive-of-your-personal-accounts-data.md

@@ -39,7 +39,8 @@ The generated `tar.gz` file reflects the data stored at the time you started the
 
 ## Deleting access to an archive of your personal account's data
 
+You can disable the download link sent to your email before an export expires by deleting the export.
+
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.account_settings %}
-3. To disable the download link sent to your email before it expires, under "Export account data", find the data export download you want to disable and click **Delete**.
-![Delete personal data export package button highlighted](/assets/images/help/repository/delete-export-personal-account-data.png)
+3. In the "Export account data" section, next to the data export download you want to disable, click **Delete**.

content/get-started/quickstart/create-a-repo.md

@@ -33,10 +33,10 @@ You can store a variety of projects in {% data variables.product.product_name %}
 
 {% note %}
 
-**Notes:** 
-- You can create public repositories for an open source project. When creating your public repository, make sure to include a [license file](https://choosealicense.com/) that determines how you want your project to be shared with others. {% data reusables.open-source.open-source-guide-repositories %} 
-- {% data reusables.open-source.open-source-learning %} 
-- You can also add community health files to your repositories, to set guidelines on how to contribute, keep your repositories safe, and much more. For more information, see "[AUTOTITLE](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)." 
+**Notes:**
+- You can create public repositories for an open source project. When creating your public repository, make sure to include a [license file](https://choosealicense.com/) that determines how you want your project to be shared with others. {% data reusables.open-source.open-source-guide-repositories %}
+- {% data reusables.open-source.open-source-learning %}
+- You can also add community health files to your repositories, to set guidelines on how to contribute, keep your repositories safe, and much more. For more information, see "[AUTOTITLE](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)."
 
 {% endnote %}
 
@@ -62,8 +62,8 @@ Congratulations! You've successfully created your first repository, and initiali
 {% data reusables.cli.cli-learn-more %}
 
 1. In the command line, navigate to the directory where you would like to create a local clone of your new project.
-2. To create a repository for your project, use the `gh repo create` subcommand. When prompted, select **Create a new repository on GitHub from scratch** and enter the name of your new project. If you want your project to belong to an organization instead of to your personal account, specify the organization name and project name with `organization-name/project-name`. 
-3. Follow the interactive prompts. To clone the repository locally, confirm yes when asked if you would like to clone the remote project directory.  
+2. To create a repository for your project, use the `gh repo create` subcommand. When prompted, select **Create a new repository on GitHub from scratch** and enter the name of your new project. If you want your project to belong to an organization instead of to your personal account, specify the organization name and project name with `organization-name/project-name`.
+3. Follow the interactive prompts. To clone the repository locally, confirm yes when asked if you would like to clone the remote project directory.
 4. Alternatively, to skip the prompts supply the repository name and a visibility flag (`--public`, `--private`, or `--internal`). For example, `gh repo create project-name --public`. To clone the repository locally, pass the `--clone` flag.  For more information about possible arguments, see the [GitHub CLI manual](https://cli.github.com/manual/gh_repo_create).
 
 {% endcli %}
@@ -80,9 +80,8 @@ Let's commit a change to the *README* file.
 
 1. In your repository's list of files, click ***README.md***.
   ![README file in file list](/assets/images/help/repository/create-commit-open-readme.png)
-2. Above the file's content, click {% octicon "pencil" aria-label="The edit icon" %}.
-3. On the **Edit file** tab, type some information about yourself.
-  ![New content in file](/assets/images/help/repository/edit-readme-light.png)
+{% data reusables.repositories.edit-file-button %}
+3. In the text box, type some information about yourself.
 {% data reusables.files.preview_change %}
 5. Review the changes you made to the file. You will see the new content in green.
   ![File preview view](/assets/images/help/repository/create-commit-review.png)

content/get-started/quickstart/hello-world.md

@@ -114,7 +114,7 @@ You can even open pull requests in your own repository and merge them yourself.
 3. In the **Example Comparisons** box, select the branch you made, `readme-edits`, to compare with `main` (the original).
 4. Look over your changes in the diffs on the Compare page, make sure they're what you want to submit.
 
-   ![diff example](/assets/images/help/repository/diffs.png)
+   ![Screenshot of a diff for the README.md file. 3 red lines list the text that's being removed, and 3 green lines list the text being added.](/assets/images/help/repository/diffs.png)
 
 5. Click **Create pull request**.
 6. Give your pull request a title and write a brief description of your changes. You can include emojis and drag and drop images and gifs.

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

@@ -25,7 +25,8 @@ type: how_to
     - 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**.
-  ![Edit milestone option](/assets/images/help/repository/edit-milestone.png)
+
+       ![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)
 5. Type the milestone's title, description, or other changes, and click **Create milestone** or **Save changes**. Milestones will render Markdown syntax. For more information about Markdown syntax, see "[AUTOTITLE](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)."
 
 ## Deleting milestones
@@ -35,12 +36,6 @@ When you delete milestones, issues and pull requests are not affected.
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-issue-pr %}
 {% data reusables.project-management.milestones %}
-4. Next to the milestone you want to delete, click **Delete**.
-![Delete milestone option](/assets/images/help/repository/delete-milestone.png)
+1. Next to the milestone you want to delete, click **Delete**.
 
-## Further reading
-
-- "[AUTOTITLE](/issues/using-labels-and-milestones-to-track-work/about-milestones)"
-- "[AUTOTITLE](/issues/using-labels-and-milestones-to-track-work/associating-milestones-with-issues-and-pull-requests)"
-- "[AUTOTITLE](/issues/using-labels-and-milestones-to-track-work/viewing-your-milestones-progress)"
-- "[AUTOTITLE](/issues/using-labels-and-milestones-to-track-work/filtering-issues-and-pull-requests-by-milestone)"
+![Screenshot of the list of milestones for a repository. Within the entry for the "beta release" milestone, a red "Delete" link is outlined in dark orange.](/assets/images/help/repository/delete-milestone.png)

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

@@ -99,9 +99,7 @@ When you create a branch rule, the branch you specify doesn't have to exist yet
    -  Optionally, to allow fork syncing, select **Allow fork syncing**.
 ![Screenshot of the checkbox to allow fork syncing](/assets/images/help/repository/lock-branch-forksync.png)
 {%- endif %}
-1. Optionally, select {% ifversion bypass-branch-protections %}**Do not allow bypassing the above settings**.
-![Do not allow bypassing the above settings checkbox](/assets/images/help/repository/do-not-allow-bypassing-the-above-settings.png){% else %}**Apply the rules above to administrators**.
-![Apply the rules above to administrators checkbox](/assets/images/help/repository/include-admins-protected-branches.png){% endif %}
+1. Optionally, select {% ifversion bypass-branch-protections %}**Do not allow bypassing the above settings**{% else %}**Apply the rules above to administrators**{% endif %}.
 1. Optionally,{% ifversion fpt or ghec %} in public repositories owned by a {% data variables.product.prodname_free_user %} organization and in all repositories owned by an organization using {% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %},{% endif %} enable branch restrictions.
    - Select **Restrict who can push to matching branches**.
      ![Branch restriction checkbox](/assets/images/help/repository/restrict-branch.png){% ifversion restrict-pushes-create-branch %}
@@ -127,7 +125,6 @@ When you create a branch rule, the branch you specify doesn't have to exist yet
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.repository-branches %}
 1. To the right of the branch protection rule you want to edit, click **Edit**.
-  ![Edit button](/assets/images/help/repository/edit-branch-protection-rule.png)
 1. Make your desired changes to the branch protection rule.
 1. Click **Save changes**.
   ![Save changes button](/assets/images/help/repository/save-branch-protection-rule.png)

content/repositories/working-with-files/managing-files/deleting-files-in-a-repository.md

@@ -38,8 +38,9 @@ If the file{% ifversion fpt or ghes or ghec %} or directory{% endif %} you delet
 ## Deleting a directory
 
 1. Browse to the directory in your repository that you want to delete.
-1. In the top-right corner, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete directory**.
-  ![Button to delete a directory](/assets/images/help/repository/delete-directory-button.png)
+1. In the top-right corner, select the {% octicon "kebab-horizontal" aria-label="More options" %} dropdown menu, then click **Delete directory**.
+
+  ![Screenshot of the file list for a directory. To the right of the directory name, a button, labeled with a kebab icon, is outlined in dark orange.](/assets/images/help/repository/delete-directory-button.png)
 1. Review the files you will delete.
 {% data reusables.files.write_commit_message %}
 {% data reusables.files.choose-commit-email %}

content/repositories/working-with-files/managing-files/editing-files.md

@@ -35,8 +35,7 @@ shortTitle: Edit files
 
 1. In your repository, browse to the file you want to edit.
 {% data reusables.repositories.edit-file %}
-3. On the **Edit file** tab, make any changes you need to the file.
-![New content in file](/assets/images/help/repository/edit-readme-light.png)
+3. In the text box, make any changes you need to the file.
 {% data reusables.files.preview_change %}
 {% data reusables.files.write_commit_message %}
 {% data reusables.files.choose-commit-email %}
@@ -48,11 +47,8 @@ shortTitle: Edit files
 When you edit a file in another user's repository, we'll automatically [fork the repository](/get-started/quickstart/fork-a-repo) and [open a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request) for you.
 
 1. In another user's repository, browse to the folder that contains the file you want to edit. Click the name of the file you want to edit.
-1. Above the file content, click {% octicon "pencil" aria-label="The edit icon" %}. At this point, GitHub forks the repository for you.
-1. Make any changes you need to the file.
-
-   ![New content in file](/assets/images/help/repository/edit-readme-light.png)
-
+2. Above the file content, click {% octicon "pencil" aria-label="Edit file" %}. At this point, GitHub forks the repository for you.
+3. In the text box, make any changes you need to the file.
 {% data reusables.files.preview_change %}
 {% data reusables.files.write_commit_message %}
 {% data reusables.files.choose-commit-email %}

content/repositories/working-with-files/managing-files/renaming-a-file.md

@@ -32,15 +32,14 @@ Renaming a file also gives you the opportunity to [move the file to a new locati
 {% endtip %}
 
 1. In your repository, browse to the file you want to rename.
-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/edit-file-icon.png)
+{% data reusables.repositories.edit-file-button %}
 3. In the filename field, change the name of the file to the new filename you want. You can also update the contents of your file at the same time.
 ![Editing a file name](/assets/images/help/repository/changing-file-name.png)
 {% data reusables.files.write_commit_message %}
 {% data reusables.files.choose_commit_branch %}
 {% data reusables.files.propose_file_change %}
 
-## Renaming a file using the command line 
+## Renaming a file using the command line
 
 You can use the command line to rename any file in your repository.
 
@@ -71,4 +70,3 @@ Many files can be [renamed directly on {% data variables.product.product_name %}
   # {% data reusables.git.reset-head-to-previous-commit-codeblock %}
   ```
 {% data reusables.git.git-push %}
-

data/reusables/repositories/edit-file-button.md

@@ -0,0 +1,3 @@
+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)

data/reusables/repositories/edit-file.md

@@ -1,13 +1,11 @@
-1. In the upper right corner of the file view, click {% octicon "pencil" aria-label="The edit icon" %} to open the file editor.
-
-   ![Edit file button](/assets/images/help/repository/edit-file-edit-button.png)
+{% data reusables.repositories.edit-file-button %}
 
    {% ifversion githubdev-editor -%}
    {% note %}
 
-   **Note:** Instead of editing and committing the file using the default file editor, you can optionally choose to use the [github.dev code editor](/codespaces/the-githubdev-web-based-editor) by clicking the dropdown menu next to {% octicon "pencil" aria-label="The edit icon" %} and selecting **Open in github.dev**.
+   **Note:** Instead of editing and committing the file using the default file editor, you can optionally choose to use the [github.dev code editor](/codespaces/the-githubdev-web-based-editor) by selecting the {% octicon "triangle-down" aria-label="More edit options" %} dropdown menu and clicking **Open in github.dev**.
 
-   ![Edit file button dropdown](/assets/images/help/repository/edit-file-edit-dropdown.png)
+   ![Screenshot of a file. In the header, a downwards-facing triangle icon is outlined in dark orange.](/assets/images/help/repository/edit-file-edit-dropdown.png)
 
    {% endnote %}
    {%- endif %}