repo sync

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/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md

@@ -47,11 +47,9 @@ You can send an invitation to collaborate in your repository directly to someone
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4%}
-{% data reusables.repositories.click-collaborators-teams %}
-1. Click **Invite a collaborator**.
-  !["Invite a collaborator" button](/assets/images/help/repository/invite-a-collaborator-button.png)
+1. In the "Access" section of the sidebar, click **{% octicon "people" aria-hidden="true" %} Collaborators**.
+1. Click **Add people**.
 2. In the search field, start typing the name of person you want to invite, then click a name in the list of matches.
-  ![Search field for typing the name of a person to invite to the repository](/assets/images/help/repository/manage-access-invite-search-field-user.png)
 3. Click **Add NAME to REPOSITORY**.
     ![Button to add collaborator](/assets/images/help/repository/add-collaborator-user-repo.png)
 {% else %}

content/actions/creating-actions/creating-a-javascript-action.md

@@ -267,9 +267,9 @@ 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.
+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**.
 
-![A screenshot of using your action in a workflow](/assets/images/help/repository/javascript-action-workflow-run-updated-2.png)
+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. To see the timestamp, click **Get the output time**.
 
 ## Template repositories for creating JavaScript actions
 

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**.
-
-   ![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)
+1. Under "Release Action", select **Publish this 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.
+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/actions/managing-workflow-runs/canceling-a-workflow.md

@@ -20,7 +20,6 @@ versions:
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
 1. From the list of workflow runs, click the name of the `queued` or `in progress` run that you want to cancel.
-![Name of workflow run](/assets/images/help/repository/in-progress-run.png)
 1. In the upper-right corner of the workflow, click **Cancel workflow**.
 ![Cancel check suite button](/assets/images/help/repository/cancel-check-suite-updated.png)
 

content/apps/using-github-apps/reviewing-your-authorized-integrations.md

@@ -16,12 +16,6 @@ topics:
   - Access management
 shortTitle: Authorized integrations
 ---
-## Reviewing your authorized {% data variables.product.prodname_oauth_apps %}
-
-{% data reusables.user-settings.access_settings %}
-{% data reusables.user-settings.access_applications %}
-{% data reusables.user-settings.access_authorized_oauth_apps %}
-{% data reusables.user-settings.review-oauth-apps %}
 
 ## Reviewing your authorized {% data variables.product.prodname_github_apps %}
 

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/moderating-comments-and-conversations/locking-conversations.md

@@ -24,14 +24,10 @@ While a conversation is locked, only [people with write access](/organizations/m
 To search for locked conversations in a repository that is not archived, you can use the search qualifiers `is:locked` and `archived:false`. Conversations are automatically locked in archived repositories. For more information, see "[AUTOTITLE](/search-github/searching-on-github/searching-issues-and-pull-requests#search-based-on-whether-a-conversation-is-locked)."
 
 1. Optionally, write a comment explaining why you're locking the conversation.
-2. In the right margin of the issue or pull request, or above the comment box on the commit page, click **Lock conversation**.
-![Lock conversation link](/assets/images/help/repository/lock-conversation.png)
-3. Optionally, choose a reason for locking the conversation.
-![Reason for locking a conversation menu](/assets/images/help/repository/locking-conversation-reason-menu.png)
-4. Read the information about locking conversations and click **Lock conversation on this issue**, **Lock conversation on this pull request**, or **Lock conversation on this commit**.
-![Confirm lock with a reason dialog box](/assets/images/help/repository/lock-conversation-confirm-with-reason.png)
-5. When you're ready to unlock the conversation, click **Unlock conversation**.
-![Unlock conversation link](/assets/images/help/repository/unlock-conversation.png)
+1. In the right sidebar of the issue or pull request, or above the comment box on the commit page, click **Lock conversation**.
+1. Optionally, select the **Choose a reason** dropdown menu, then click a reason for locking the conversation.
+1. Read the information about locking conversations and click **Lock conversation on this issue**, **Lock conversation on this pull request**, or **Lock conversation on this commit**.
+1. When you're ready to unlock the conversation, in the right sidebar of the issue or pull request, or above the comment box on the commit page, click **Unlock conversation**.
 
 ## Further reading
 
@@ -40,5 +36,4 @@ To search for locked conversations in a repository that is not archived, you can
 - "[AUTOTITLE](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"{% ifversion fpt or ghec %}
 - "[AUTOTITLE](/communities/maintaining-your-safety-on-github)"
 - "[AUTOTITLE](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)"
-- "[AUTOTITLE](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)"
 {% endif %}

content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md

@@ -22,7 +22,7 @@ shortTitle: Manage comments
 
 If a comment is off-topic, outdated, or resolved, you may want to hide a comment to keep a discussion focused or make a pull request easier to navigate and review. Hidden comments are minimized but people with read access to the repository can expand them.
 
-![Minimized comment](/assets/images/help/repository/hidden-comment.png)
+![Screenshot of a hidden comment. The only visible content is "This comment has been minimized", with a button to show the comment.](/assets/images/help/repository/hidden-comment.png)
 
 1. Navigate to the comment you'd like to hide.
 2. In the upper-right corner of the comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Hide**.
@@ -39,9 +39,8 @@ If a comment is off-topic, outdated, or resolved, you may want to hide a comment
 {% ifversion fpt or ghec %}Organization moderators, and anyone{% else %}Anyone{% endif %} with write access to a repository, can unhide comments on issues, pull requests, and commits.
 
 1. Navigate to the comment you'd like to unhide.
-2. In the upper-right corner of the comment, click **{% octicon "fold" aria-label="The fold icon" %} Show comment**.
-   ![Show comment text](/assets/images/help/repository/hidden-comment-show.png)
-3. On the right side of the expanded comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then **Unhide**.
+1. On the right side of the comment, click **{% octicon "fold" aria-hidden="true" %} Show comment**.
+1. On the right side of the expanded comment, select the {% octicon "kebab-horizontal" aria-label="Show options" %} dropdown menu, then click **Unhide**.
    ![The horizontal kebab icon and comment moderation menu showing the edit, unhide, delete options](/assets/images/help/repository/comment-menu-hidden.png)
 
 ## Editing 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/adding-a-license-to-a-repository.md

@@ -24,18 +24,16 @@ Open source licenses enable others to freely use, change, and distribute the pro
 {% ifversion fpt or ghec %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.files.add-file %}
-3. In the file name field, type *LICENSE* or *LICENSE.md* (with all caps).
-4. To the right of the file name field, click **Choose a license template**.
-  ![Choose a license template button](/assets/images/help/repository/license-tool.png)
-5. On the left side of the page, under "Add a license to your project," review the available licenses, then select a license from the list.
-  ![List of available licenses](/assets/images/help/repository/license-tool-picker.png)
-6. Click **Review and submit**.
-  ![Review and submit button](/assets/images/help/repository/license-review-tool.png)
+1. In the file name field, type *LICENSE* or *LICENSE.md* (with all caps).
+1. Under the file name, click **Choose a license template**.
+
+   ![Screenshot of the new file form, with "LICENSE" entered in the file name field. A button, labeled "Choose a license template," is outlined in dark orange.](/assets/images/help/repository/license-tool.png)
+1. On the left side of the page, under "Add a license to your project," review the available licenses, then select a license from the list.
+1. Click **Review and submit**.
 {% data reusables.files.write_commit_message %}
 {% data reusables.files.choose_commit_branch %}
 {% data reusables.files.choose-commit-email %}
-10. Click **Commit new file**.
-  ![Commit license to branch](/assets/images/help/repository/license-submit-tool.png)
+1. Click **Commit new file**.
 
 {% endif %}
 
@@ -50,8 +48,7 @@ Open source licenses enable others to freely use, change, and distribute the pro
 {% data reusables.files.choose-commit-email %}
 7. Below the commit message fields, decide whether to add your commit to the current branch or to a new branch. If your current branch is `main`, you should choose to create a new branch for your commit and then create a pull request. For more information, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)".
 ![Commit branch options](/assets/images/help/repository/choose-commit-branch.png)
-8. Click **Commit new file**.
-  ![Commit license to branch](/assets/images/help/repository/license-submit-tool.png)
+1. Click **Commit new file**.
 
 {% endif %}
 

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.