Merge branch 'main' into copilot-enterprise-megabranch

content/actions/automating-builds-and-tests/building-and-testing-python.md

@@ -425,7 +425,7 @@ jobs:
       - name: Build package
         run: python -m build
       - name: Publish package
-        uses: pypa/gh-action-pypi-publish@v1
+        uses: pypa/gh-action-pypi-publish@release/v1
         with:
           password: {% raw %}${{ secrets.PYPI_API_TOKEN }}{% endraw %}
 ```

content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md

@@ -261,7 +261,7 @@ You can also delete environments through the REST API. For more information, see
 
 {% data reusables.actions.environment-deployment-event %}
 
-You can access these objects through the REST API or GraphQL API. You can also subscribe to these webhook events. For more information, see "[AUTOTITLE](/rest/repos#deployments)" (REST API), "[AUTOTITLE](/graphql/reference/objects#deployment)" (GraphQL API), or "[AUTOTITLE](/webhooks-and-events/webhooks/webhook-events-and-payloads#deployment)."
+You can access these objects through the REST API or GraphQL API. You can also subscribe to these webhook events. For more information, see "[AUTOTITLE](/rest/repos#deployments)," "[AUTOTITLE](/graphql/reference/objects#deployment)" (GraphQL API), or "[AUTOTITLE](/webhooks-and-events/webhooks/webhook-events-and-payloads#deployment)."
 
 ## Next steps
 

content/actions/quickstart.md

@@ -24,8 +24,8 @@ The following example shows you how {% data variables.product.prodname_actions %
 
 ## Creating your first workflow
 
-1. Create a `.github/workflows` directory in  your repository on {% data variables.product.prodname_dotcom %} if this directory does not already exist.
+1. Create a `.github/workflows` directory in  your repository on {% data variables.product.prodname_dotcom %} if this directory does not already exist. The directory must have this exact name in order for {% data variables.product.prodname_dotcom %} to discover any {% data variables.product.prodname_actions %} workflows that it contains.
-1. In the `.github/workflows` directory, create a file named `github-actions-demo.yml`. For more information, see "[AUTOTITLE](/repositories/working-with-files/managing-files/creating-new-files)."
+1. In the `.github/workflows` directory, create a file with the `.yml` or `.yaml` extension. This tutorial will use `github-actions-demo.yml` as the file name. For more information, see "[AUTOTITLE](/repositories/working-with-files/managing-files/creating-new-files)."
 1. Copy the following YAML contents into the `github-actions-demo.yml` file:
 
    ```yaml copy

content/actions/using-workflows/events-that-trigger-workflows.md

@@ -154,7 +154,7 @@ on:
 | --------------------- | -------------- | ------------ | -------------|
 | [`deployment`](/webhooks-and-events/webhooks/webhook-events-and-payloads#deployment) | Not applicable | Commit to be deployed | Branch or tag to be deployed (empty if created with a commit SHA)|
 
-Runs your workflow when someone creates a deployment in the workflow's repository. Deployments created with a commit SHA may not have a Git ref. For information about the APIs to create a deployment, see "[AUTOTITLE](/graphql/reference/mutations#createdeployment)" in the GraphQL API documentation or "[AUTOTITLE](/rest/repos#deployments)" in the REST API documentation.
+Runs your workflow when someone creates a deployment in the workflow's repository. Deployments created with a commit SHA may not have a Git ref. For information about the APIs to create a deployment, see "[AUTOTITLE](/graphql/reference/mutations#createdeployment)" in the GraphQL API documentation or "[AUTOTITLE](/rest/repos#deployments)."
 
 For example, you can run a workflow when the `deployment` event occurs.
 

content/admin/identity-and-access-management/provisioning-user-accounts-for-enterprise-managed-users/provisioning-users-with-scim-using-the-rest-api.md

@@ -125,7 +125,7 @@ You can view this mapping on {% data variables.location.product_location %}. For
 
 ### Ensuring users have the access you intend
 
-If your integration manages access using groups on your IdP, you can validate that users get the access you intend. You can use the REST API to compare your IdP's group memberships with {% data variables.product.prodname_dotcom %}'s understanding of those groups. For more information, see "[AUTOTITLE](/rest/teams/external-groups#about-external-groups)" and "[AUTOTITLE](/rest/teams/teams#get-a-team-by-name)" in the REST API documentation.
+If your integration manages access using groups on your IdP, you can validate that users get the access you intend. You can use the REST API to compare your IdP's group memberships with {% data variables.product.prodname_dotcom %}'s understanding of those groups. For more information, see "[AUTOTITLE](/rest/teams/external-groups#about-external-groups)" and "[AUTOTITLE](/rest/teams/teams#get-a-team-by-name)."
 
 ### About suspension and reprovisioning of users
 

content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md

@@ -91,7 +91,7 @@ The `$GITHUB_VIA` variable is available in the pre-receive hook environment when
 | <pre>git refs create api</pre> | Creation of a ref via the API | "[AUTOTITLE](/rest/git#create-a-reference)" |
 | <pre>git refs delete api</pre> | Deletion of a ref via the API | "[AUTOTITLE](/rest/git#delete-a-reference)" |
 | <pre>git refs update api</pre> | Update of a ref via the API | "[AUTOTITLE](/rest/git#update-a-reference)" |
-| <pre>git repo contents api</pre> | Change to a file's contents via the API | "[AUTOTITLE](/rest/repos#create-or-update-file-contents)" in the REST API documentation |
+| <pre>git repo contents api</pre> | Change to a file's contents via the API | "[AUTOTITLE](/rest/repos#create-or-update-file-contents)" |
 {%- ifversion ghes %}
 | `merge` | Merge of a pull request using auto-merge | "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)" |
 {%- endif %}

content/code-security/secret-scanning/push-protection-for-repositories-and-organizations.md

@@ -58,7 +58,7 @@ For information on the secrets and service providers supported for push protecti
 
 For you to use {% data variables.product.prodname_secret_scanning %} as a push protection in public repositories, the {% ifversion secret-scanning-enterprise-level %}enterprise,{% endif %} organization{% ifversion secret-scanning-enterprise-level %},{% endif %} or repository needs to have {% data variables.product.prodname_secret_scanning %} enabled.{% ifversion secret-scanning-push-protection-private-internal %} To use {% data variables.product.prodname_secret_scanning %} as a push protection in private or internal repositories,{% ifversion secret-scanning-user-owned-repos %} or in user-owned repositories{% ifversion ghec %} for {% data variables.product.prodname_emus %}{% endif %},{% endif %} the enterprise or organization also needs to have {% data variables.product.prodname_GH_advanced_security %} enabled.{% endif %} For more information, see {% ifversion secret-scanning-enterprise-level %}"[AUTOTITLE](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise),"{% endif %} "[AUTOTITLE](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)," "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)," and "[AUTOTITLE](/get-started/learning-about-github/about-github-advanced-security)."
 
-Organization owners, security managers, and repository administrators can also enable push protection for {% data variables.product.prodname_secret_scanning %} via the API. For more information, see "[AUTOTITLE](/rest/repos#update-a-repository)" and expand the "Properties of the `security_and_analysis` object" section in the REST API documentation.
+Organization owners, security managers, and repository administrators can also enable push protection for {% data variables.product.prodname_secret_scanning %} via the API. For more information, see "[AUTOTITLE](/rest/repos#update-a-repository)" and expand the "Properties of the `security_and_analysis` object" section.
 
 {% ifversion secret-scanning-enterprise-level-api %}
 Enterprise administrators can also enable or disable {% data variables.product.prodname_secret_scanning %} as a push protection for the enterprise via the API. For more information, see "[AUTOTITLE](/rest/enterprise-admin/code-security-and-analysis)" in the REST API documentation.{% endif %}

content/contributing/style-guide-and-content-model/style-guide.md

@@ -65,7 +65,7 @@ For more information on formatting callouts, see “Callouts” in "[AUTOTITLE](
 
 Landing pages and some articles have buttons that take people to relevant content in other articles or on other {% data variables.product.prodname_dotcom %} webpages. Buttons should be used when someone needs to navigate to another page to complete the task being described. For example, "[AUTOTITLE](/enterprise-cloud@latest/admin/overview/setting-up-a-trial-of-github-enterprise-cloud)" has a button that takes people to the trial sign up page since that is the next step in the process of setting up a trial. The "[AUTOTITLE](/migrations)" landing page uses a button to direct people to the article that most people will need to read to start a migration.
 
-If a button encourages people to navigate away from the {% data variables.product.prodname_docs %} site, follow the call to action (CTA) button guidelines. If you want to include another type of button on a landing page or article, open an issue in the `docs-strategy` repository to share your use case for approval by the Content Strategy team.
+If a button encourages people to navigate away from the {% data variables.product.prodname_docs %} site, follow the call to action (CTA) button guidelines. If you want to include another type of button on a landing page or article, you must get approval from the {% data variables.product.prodname_docs %} team.
 
 ## Call to action (CTA) buttons
 

content/migrations/overview/programmatically-importing-repositories.md

@@ -25,7 +25,7 @@ On April 12, 2024, {% data variables.product.company_short %} will deprecate all
 
 If the source repository is on {% data variables.product.prodname_dotcom_the_website %}, you may be able to use a fork instead of importing the repository. {% data reusables.repositories.about-forks %} For more information, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)."
 
-You can programmatically fork a repository using the REST API. For more information, see "[AUTOTITLE](/rest/repos/forks)" in the REST API documentation.
+You can programmatically fork a repository using the REST API. For more information, see "[AUTOTITLE](/rest/repos/forks)."
 
 If your use case meets any of the following criteria, you can't use forking instead of directly importing your repository.
 
@@ -38,7 +38,7 @@ If the source repository is on {% data variables.product.prodname_dotcom_the_web
 
 To use repository templates, you must either have read access to an existing repository that's a template, or you must have access to create a template.
 
-You can programmatically create a repository from a repository template using the REST API. For more information, see "[AUTOTITLE](/rest/repos/repos)" in the REST API documentation.
+You can programmatically create a repository from a repository template using the REST API. For more information, see "[AUTOTITLE](/rest/repos/repos)."
 
 ## Using {% data variables.product.prodname_importer_proper_name %}
 
@@ -64,4 +64,4 @@ If the source repository is a Git repository, you can call the {% data variables
 
 ## Further reading
 
-- "[AUTOTITLE](/rest/repos/repos)" in the REST API documentation
+- "[AUTOTITLE](/rest/repos/repos)"

content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations.md

@@ -26,7 +26,7 @@ If you use SAML SSO without implementing SCIM, you won't have automatic deprovis
 
 ## Supported identity providers
 
-These identity providers (IdPs) are compatible with the {% data variables.product.product_name %} SCIM API for organizations. For more information, see [SCIM](/rest/scim) in the {% ifversion ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API documentation.
+These identity providers (IdPs) are compatible with the {% data variables.product.product_name %} SCIM API for organizations. For more information, see "[AUTOTITLE](/rest/scim)."
 - Microsoft Entra ID (previously known as Azure AD)
 - Okta
 - OneLogin

content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management-for-your-organization.md

@@ -92,7 +92,7 @@ For more information on using the GraphQL API, see:
 
 You can re-provision SCIM for users manually through your IdP. For example, to resolve provisioning errors for Okta, in the Okta admin portal, you can unassign and reassign users to the {% data variables.product.prodname_dotcom %} app. This should trigger Okta to make an API call to populate the SCIM metadata for these users on {% data variables.product.prodname_dotcom %}. For more information, see "[Unassign users from applications](https://help.okta.com/en/prod/Content/Topics/users-groups-profiles/usgp-unassign-apps.htm)" or "[Assign users to applications](https://help.okta.com/en/prod/Content/Topics/users-groups-profiles/usgp-assign-apps.htm)" in the Okta documentation.
 
-To confirm that a user's SCIM identity is created, we recommend testing this process with a single organization member whom you have confirmed doesn't have a SCIM external identity. After manually updating the users in your IdP, you can check if the user's SCIM identity was created using the SCIM API or on {% data variables.product.prodname_dotcom %}. For more information, see "[Auditing users for missing SCIM metadata](#auditing-users-for-missing-scim-metadata)" or the REST API endpoint "[AUTOTITLE](/rest/scim#get-scim-provisioning-information-for-a-user)."
+To confirm that a user's SCIM identity is created, we recommend testing this process with a single organization member whom you have confirmed doesn't have a SCIM external identity. After manually updating the users in your IdP, you can check if the user's SCIM identity was created using the SCIM API or on {% data variables.product.prodname_dotcom %}. For more information, see "[Auditing users for missing SCIM metadata](#auditing-users-for-missing-scim-metadata)" or "[AUTOTITLE](/rest/scim#get-scim-provisioning-information-for-a-user)."
 
 If re-provisioning SCIM for users doesn't help, please contact {% data variables.product.prodname_dotcom %} Support.
 

content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md

@@ -73,7 +73,7 @@ If you want to match two or more code owners with the same pattern, all the code
 CODEOWNERS paths are case sensitive, because {% data variables.product.prodname_dotcom %} uses a case sensitive file system. Since CODEOWNERS are evaluated by {% data variables.product.prodname_dotcom %}, even systems that are case insensitive (for example, macOS) must use paths and files that are cased correctly in the CODEOWNERS file.
 
 {% ifversion codeowners-errors %}
-If any line in your CODEOWNERS file contains invalid syntax, that line will be skipped. When you navigate to the CODEOWNERS file in your repository on {% data variables.location.product_location %}, you can see any errors highlighted. A list of errors in a repository's CODEOWNERS file is also accessible via the API. For more information, see "[AUTOTITLE](/rest/repos#list-codeowners-errors)" in the REST API documentation.
+If any line in your CODEOWNERS file contains invalid syntax, that line will be skipped. When you navigate to the CODEOWNERS file in your repository on {% data variables.location.product_location %}, you can see any errors highlighted. A list of errors in a repository's CODEOWNERS file is also accessible via the API. For more information, see "[AUTOTITLE](/rest/repos#list-codeowners-errors)."
 {% else %}
 If any line in your CODEOWNERS file contains invalid syntax, the file will not be detected and will not be used to request reviews.
 {% endif %}

content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md

@@ -101,7 +101,7 @@ Organization owners and repository administrators can only grant access to view
 
 You can allow {% data variables.product.prodname_secret_scanning %} to automatically check the validity of a secret found in your repository by sending it to the relevant partner. Alternatively, organization owners and enterprise administrators can enable the feature for all repositories in the organization or enterprise settings. For more information, see "[Allowing validity checks for partner patterns in an organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization#allowing-validity-checks-for-partner-patterns-in-an-organization)" and "[AUTOTITLE](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)."
 
-You can also use the REST API to enable validity checks for partner patterns for your repository. For more information, see "[AUTOTITLE](/rest/repos/repos#update-a-repository)" in the REST API documentation.
+You can also use the REST API to enable validity checks for partner patterns for your repository. For more information, see "[AUTOTITLE](/rest/repos/repos#update-a-repository)."
 
 {% note %}
 

content/rest/guides/using-the-rest-api-to-interact-with-your-git-database.md

@@ -17,7 +17,7 @@ redirect_from:
 This basically allows you to reimplement a lot of Git functionality with the REST API - by creating raw objects directly into the database and updating branch references you could technically do just about anything that Git can do without having Git installed.
 
 The REST API will return a `409 Conflict` if the Git repository is empty
-or unavailable.  An unavailable repository typically means {% data variables.product.product_name %} is in the process of creating the repository. For an empty repository, you can use the "[AUTOTITLE](/rest/repos#create-or-update-file-contents)" endpoint to create content and initialize the repository so you can use the API to manage the Git database. Contact {% data variables.contact.contact_support %} if this response status persists.
+or unavailable.  An unavailable repository typically means {% data variables.product.product_name %} is in the process of creating the repository. For an empty repository, you can use the [`PUT /repos/{owner}/{repo}/contents/{path}`](/rest/repos/contents#create-or-update-file-contents) REST API endpoint to create content and initialize the repository so you can use the API to manage the Git database. Contact {% data variables.contact.contact_support %} if this response status persists.
 
 For more information on the Git object database, please read the
 [Git Internals](https://git-scm.com/book/en/v2/Git-Internals-Plumbing-and-Porcelain) chapter of

content/rest/repos/autolinks.md

@@ -1,5 +1,5 @@
 ---
-title: Repository autolinks
+title: REST API endpoints for repository autolinks
 allowTitleToDifferFromFilename: true
 shortTitle: Autolinks
 intro: Use the REST API to add autolinks to external resources.

content/rest/repos/contents.md

@@ -1,5 +1,5 @@
 ---
-title: Repository contents
+title: REST API endpoints for repository contents
 allowTitleToDifferFromFilename: true
 shortTitle: Contents
 intro: >-

content/rest/repos/custom-properties.md

@@ -1,5 +1,5 @@
 ---
-title: Custom properties
+title: REST API endpoints for custom properties
 shortTitle: Custom properties
 intro: 'Use the REST API to list the custom properties assigned to a repository by the organization.'
 versions: # DO NOT MANUALLY EDIT. CHANGES WILL BE OVERWRITTEN BY A 🤖

content/rest/repos/forks.md

@@ -1,5 +1,7 @@
 ---
-title: Forks
+title: REST API endpoints for forks
+shortTitle: Forks
+allowTitleToDifferFromFilename: true
 intro: Use the REST API to manage repository forks.
 versions: # DO NOT MANUALLY EDIT. CHANGES WILL BE OVERWRITTEN BY A 🤖
   fpt: '*'

content/rest/repos/index.md

@@ -1,5 +1,6 @@
 ---
-title: Repositories
+title: REST API endpoints for repositories
+shortTitle: Repositories
 intro: >-
   Use the REST API to create, manage and control the workflow of public and
   private {% data variables.product.product_name %} repositories.

content/rest/repos/lfs.md

@@ -1,5 +1,6 @@
 ---
-title: Git LFS
+title: REST API endpoints for Git LFS
+shortTitle: Git LFS
 intro: >-
   Use the REST API to enable or disable {% data
   variables.large_files.product_name_long %} (LFS) for a repository.

content/rest/repos/repos.md

@@ -1,5 +1,6 @@
 ---
-title: Repositories
+title: REST API endpoints for repositories
+shortTitle: Repositories
 intro: >-
   Use the REST API to manage repositories on {% data
   variables.product.company_short %}.

content/rest/repos/rule-suites.md

@@ -1,6 +1,6 @@
 ---
-title: Rule Suites
+title: REST API endpoints for rule suites
-shortTitle: Rule Suites
+shortTitle: Rule suites
 intro: Use the REST API to manage rule suites for repositories.
 versions: # DO NOT MANUALLY EDIT. CHANGES WILL BE OVERWRITTEN BY A 🤖
   fpt: '*'

content/rest/repos/rules.md

@@ -1,5 +1,5 @@
 ---
-title: Rules
+title: REST API endpoints for rules
 shortTitle: Rules
 intro: >-
   Use the REST API to manage rulesets for repositories. Rulesets control how

content/rest/repos/tags.md

@@ -1,5 +1,5 @@
 ---
-title: Repository tags
+title: REST API endpoints for repository tags
 allowTitleToDifferFromFilename: true
 shortTitle: Tags
 intro: Use the REST API to manage tags for a repository.

content/rest/repos/webhooks.md

@@ -1,5 +1,5 @@
 ---
-title: Repository webhooks
+title: REST API endpoints for repository webhooks
 shortTitle: Webhooks
 intro: Use the REST API to create and manage webhooks for your repositories.
 versions: # DO NOT MANUALLY EDIT. CHANGES WILL BE OVERWRITTEN BY A 🤖

content/rest/scim/index.md

@@ -1,5 +1,7 @@
 ---
-title: SCIM
+title: REST API endpoints for SCIM
+shortTitle: SCIM
+allowTitleToDifferFromFilename: true
 intro: >-
   Use the REST API to control and manage your GitHub organization members' access
   with SCIM.

content/rest/scim/scim.md

@@ -1,5 +1,7 @@
 ---
-title: SCIM
+title: REST API endpoints for SCIM
+shortTitle: SCIM
+allowTitleToDifferFromFilename: true
 intro: >-
   Use the REST API to control and manage your GitHub organization members' access
   with SCIM.

content/rest/secret-scanning/secret-scanning.md

@@ -18,7 +18,7 @@ autogenerated: rest
 
 You can use the API to:
 
-- Enable or disable {% data variables.product.prodname_secret_scanning %}{% ifversion secret-scanning-push-protection %} and push protection{% endif %} for a repository. For more information, see "[AUTOTITLE](/rest/repos/repos#update-a-repository)" and expand the "Properties of the `security_and_analysis` object" section in the REST API documentation.
+- Enable or disable {% data variables.product.prodname_secret_scanning %}{% ifversion secret-scanning-push-protection %} and push protection{% endif %} for a repository. For more information, see "[AUTOTITLE](/rest/repos/repos#update-a-repository)" and expand the "Properties of the `security_and_analysis` object" section.
 - Retrieve and update {% data variables.secret-scanning.alerts %} from a repository. For further details, see the sections below.
 
 For more information about {% data variables.product.prodname_secret_scanning %}, see "[AUTOTITLE](/code-security/secret-scanning/about-secret-scanning)."

content/rest/teams/discussion-comments.md

@@ -1,5 +1,5 @@
 ---
-title: Team discussion comments
+title: REST API endpoints for team discussion comments
 allowTitleToDifferFromFilename: true
 shortTitle: Discussion comments
 intro: >-

content/rest/teams/discussions.md

@@ -1,5 +1,5 @@
 ---
-title: Team discussions
+title: REST API endpoints for team discussions
 allowTitleToDifferFromFilename: true
 shortTitle: Discussions
 intro: >-

content/rest/teams/external-groups.md

@@ -1,5 +1,7 @@
 ---
-title: External groups
+title: REST API endpoints for external groups
+shortTitle: External groups
+allowTitleToDifferFromFilename: true
 intro: >-
   Use the REST API to view the external identity provider groups that are
   available to your organization and manage the connection between external

content/rest/teams/index.md

@@ -1,5 +1,7 @@
 ---
-title: Teams
+title: REST API endpoints for teams
+shortTitle: Teams
+allowTitleToDifferFromFilename: true
 intro: 'Use the REST API to create and manage teams in your {% data variables.product.product_name %} organization.'
 redirect_from:
   - /v3/teams

content/rest/teams/members.md

@@ -1,5 +1,5 @@
 ---
-title: Team members
+title: REST API endpoints for team members
 intro: >-
   Use the REST API to create and manage membership of teams in your {% data
   variables.product.product_name %} organization.

content/rest/teams/team-sync.md

@@ -1,5 +1,6 @@
 ---
-title: Team synchronization
+title: REST API endpoints for team synchronization
+shortTitle: Team synchronization
 intro: >-
   Use the REST API to manage connections between {% data
   variables.product.product_name %} teams and external identity provider (IdP)

content/rest/teams/teams.md

@@ -1,5 +1,7 @@
 ---
-title: Teams
+title: REST API endpoints for teams
+shortTitle: Teams
+allowTitleToDifferFromFilename: true
 intro: >-
   Use the REST API to create and manage teams in your {% data
   variables.product.product_name %} organization.

content/rest/users/blocking.md

@@ -1,5 +1,6 @@
 ---
-title: Blocking users
+title: REST API endpoints for blocking users
+shortTitle: Blocking users
 intro: Use the REST API to manage blocked users.
 versions: # DO NOT MANUALLY EDIT. CHANGES WILL BE OVERWRITTEN BY A 🤖
   fpt: '*'

content/rest/users/emails.md

@@ -1,5 +1,7 @@
 ---
-title: Emails
+title: REST API endpoints for emails
+shortTitle: Emails
+allowTitleToDifferFromFilename: true
 intro: Use the REST API to manage email addresses of authenticated users.
 versions: # DO NOT MANUALLY EDIT. CHANGES WILL BE OVERWRITTEN BY A 🤖
   fpt: '*'

content/rest/users/followers.md

@@ -1,5 +1,7 @@
 ---
-title: Followers
+title: REST API endpoints for followers
+shortTitle: Followers
+allowTitleToDifferFromFilename: true
 intro: Use the REST API to get information about followers of authenticated users.
 versions: # DO NOT MANUALLY EDIT. CHANGES WILL BE OVERWRITTEN BY A 🤖
   fpt: '*'

content/rest/users/gpg-keys.md

@@ -1,5 +1,7 @@
 ---
-title: GPG Keys
+title: REST API endpoints for GPG keys
+shortTitle: GPG keys
+allowTitleToDifferFromFilename: true
 intro: Use the REST API to manage GPG keys of authenticated users.
 versions: # DO NOT MANUALLY EDIT. CHANGES WILL BE OVERWRITTEN BY A 🤖
   fpt: '*'

content/rest/users/index.md

@@ -1,5 +1,7 @@
 ---
-title: Users
+title: REST API endpoints for users
+shortTitle: Users
+allowTitleToDifferFromFilename: true
 intro: Use the REST API to get public and private information about authenticated users.
 redirect_from:
   - /v3/users

content/rest/users/keys.md

@@ -1,5 +1,6 @@
 ---
-title: Git SSH Keys
+title: REST API endpoints for Git SSH keys
+shortTitle: Git SSH keys
 intro: Use the REST API to manage Git SSH keys of authenticated users.
 versions: # DO NOT MANUALLY EDIT. CHANGES WILL BE OVERWRITTEN BY A 🤖
   fpt: '*'

content/rest/users/social-accounts.md

@@ -1,5 +1,7 @@
 ---
-title: Social accounts
+title: REST API endpoints for social accounts
+shortTitle: Social accounts
+allowTitleToDifferFromFilename: true
 intro: Use the REST API to manage social accounts of authenticated users.
 versions: # DO NOT MANUALLY EDIT. CHANGES WILL BE OVERWRITTEN BY A 🤖
   fpt: '*'

content/rest/users/ssh-signing-keys.md

@@ -1,5 +1,6 @@
 ---
-title: SSH signing keys
+title: REST API endpoints for SSH signing keys
+shortTitle: SSH signing keys
 intro: Use the REST API to manage SSH signing keys of authenticated users.
 versions:
   fpt: '*'

content/rest/users/users.md

@@ -1,5 +1,7 @@
 ---
-title: Users
+title: REST API endpoints for users
+shortTitle: Users
+allowTitleToDifferFromFilename: true
 intro: >-
   Use the REST API to get public and private information about authenticated
   users.

content/support/learning-about-github-support/about-ticket-priority.md

@@ -55,6 +55,22 @@ Ticket priority helps to ensure that support requests are handled in order, and
 | {% data variables.product.support_ticket_priority_normal %} | {% data variables.product.prodname_advanced_security %} is functioning inconsistently, causing impaired end user usage and productivity. |
 | {% data variables.product.support_ticket_priority_low %} | {% data variables.product.prodname_advanced_security %} is functioning consistently, but the end user requests minor changes in the software, such as documentation updates, cosmetic defects, or enhancements.|
 
+{% ifversion ghes != 3.8 %}
+
+## Ticket priorities for {% data variables.product.prodname_actions_runner_controller %}  (ARC)
+
+| Priority | Description | Examples |
+| :---: | --- | --- |
+| {% data variables.product.support_ticket_priority_urgent %}{% ifversion ghec %}<br><br>([{% data variables.contact.premium_support %}](/support/learning-about-github-support/about-github-premium-support) only){% endif %} | Issues that critically impact the functionality of GitHub-supported ARC in an existing production environment. | ARC fails to create pods/start job/remove pods, or ARC has a significant bug affecting production and a rollback is not possible. |
+| {% data variables.product.support_ticket_priority_high %} | Issues that affect the performance of  {% data variables.product.prodname_dotcom %}-supported ARC in an existing production environment but do not result in a complete system failure. | Delays in pod termination or assignment of jobs to pods, where the delay is not in line with expectations but does not entirely halt the workflow. |
+| {% data variables.product.support_ticket_priority_normal %} / {% data variables.product.support_ticket_priority_low %} | Any other minor issues not classified as {% data variables.product.support_ticket_priority_urgent %} or {% data variables.product.support_ticket_priority_high %} should be directed to [the open source {% data variables.product.prodname_actions_runner_controller %} repository](https://github.com/actions/actions-runner-controller) issues/discussions.  | Customization, performance analysis, initial setup. |
+
+For more information about what {% data variables.contact.github_support %} can assist with, see [AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/about-support-for-actions-runner-controller).
+
+If you are uncertain if the issue is out of scope, contact {% data variables.contact.contact_support_page %} and we're happy to help you determine the best way to proceed.
+
+{% endif %}
+
 ## Further reading
 
 - "[AUTOTITLE](/support/contacting-github-support/creating-a-support-ticket)"

data/graphql/ghec/schema.docs.graphql

@@ -19561,7 +19561,7 @@ type LinkedBranch implements Node {
 }
 
 """
-The connection type for LinkedBranch.
+A list of branches linked to an issue.
 """
 type LinkedBranchConnection {
   """
@@ -19771,7 +19771,7 @@ type Mannequin implements Actor & Node & UniformResourceLocatable {
 }
 
 """
-The connection type for Mannequin.
+A list of mannequins.
 """
 type MannequinConnection {
   """
@@ -29932,7 +29932,7 @@ enum OrganizationInvitationType {
 }
 
 """
-The connection type for User.
+A list of users who belong to the organization.
 """
 type OrganizationMemberConnection {
   """
@@ -45696,7 +45696,7 @@ type RepositoryMigration implements Migration & Node {
 }
 
 """
-The connection type for RepositoryMigration.
+A list of migrations.
 """
 type RepositoryMigrationConnection {
   """
@@ -49277,7 +49277,7 @@ enum SponsorAndLifetimeValueOrderField {
 }
 
 """
-The connection type for Sponsor.
+A list of users and organizations sponsoring someone via GitHub Sponsors.
 """
 type SponsorConnection {
   """
@@ -51762,7 +51762,7 @@ type Sponsorship implements Node {
 }
 
 """
-The connection type for Sponsorship.
+A list of sponsorships either from the subject or received by the subject.
 """
 type SponsorshipConnection {
   """
@@ -61075,7 +61075,7 @@ type UserBlockedEvent implements Node {
 }
 
 """
-The connection type for User.
+A list of users.
 """
 type UserConnection {
   """

data/graphql/schema.docs.graphql

@@ -19561,7 +19561,7 @@ type LinkedBranch implements Node {
 }
 
 """
-The connection type for LinkedBranch.
+A list of branches linked to an issue.
 """
 type LinkedBranchConnection {
   """
@@ -19771,7 +19771,7 @@ type Mannequin implements Actor & Node & UniformResourceLocatable {
 }
 
 """
-The connection type for Mannequin.
+A list of mannequins.
 """
 type MannequinConnection {
   """
@@ -29932,7 +29932,7 @@ enum OrganizationInvitationType {
 }
 
 """
-The connection type for User.
+A list of users who belong to the organization.
 """
 type OrganizationMemberConnection {
   """
@@ -45696,7 +45696,7 @@ type RepositoryMigration implements Migration & Node {
 }
 
 """
-The connection type for RepositoryMigration.
+A list of migrations.
 """
 type RepositoryMigrationConnection {
   """
@@ -49277,7 +49277,7 @@ enum SponsorAndLifetimeValueOrderField {
 }
 
 """
-The connection type for Sponsor.
+A list of users and organizations sponsoring someone via GitHub Sponsors.
 """
 type SponsorConnection {
   """
@@ -51762,7 +51762,7 @@ type Sponsorship implements Node {
 }
 
 """
-The connection type for Sponsorship.
+A list of sponsorships either from the subject or received by the subject.
 """
 type SponsorshipConnection {
   """
@@ -61075,7 +61075,7 @@ type UserBlockedEvent implements Node {
 }
 
 """
-The connection type for User.
+A list of users.
 """
 type UserConnection {
   """

data/reusables/dependabot/automatically-pause-dependabot-updates.md

@@ -17,7 +17,7 @@ When {% data variables.product.prodname_dependabot %} is paused, {% data variabl
 - To the UI of the **Settings** tab of the repository (under **Code security and analysis**, then **{% data variables.product.prodname_dependabot %}**).
 - To the list of {% data variables.product.prodname_dependabot_alerts %} (if {% data variables.product.prodname_dependabot_security_updates %} are affected).
 
-{% ifversion dependabot-updates-paused-enterprise-orgs %} Additionally, you will be able to see whether {% data variables.product.prodname_dependabot %} is paused at the organization-level in the security overview. The `paused` status will also be visible via the API. For more information, see "[AUTOTITLE](/rest/repos#enable-automated-security-fixes)" in the REST API documentation.{% endif %}
+{% ifversion dependabot-updates-paused-enterprise-orgs %} Additionally, you will be able to see whether {% data variables.product.prodname_dependabot %} is paused at the organization-level in the security overview. The `paused` status will also be visible via the API. For more information, see "[AUTOTITLE](/rest/repos#enable-automated-security-fixes)."{% endif %}
 
 As soon as a maintainer interacts with a {% data variables.product.prodname_dependabot %} pull request again, {% data variables.product.prodname_dependabot %} will unpause itself:
 - Security updates are automatically resumed for {% data variables.product.prodname_dependabot_alerts %}.

data/reusables/webhooks/fork_short_desc.md

@@ -1 +1 @@
-A user forks a repository. For more information, see the "[AUTOTITLE](/rest/repos#forks)" REST API.
+A user forks a repository. For more information, see "[AUTOTITLE](/rest/repos#forks)."

src/graphql/data/fpt/schema.json

@@ -30510,7 +30510,7 @@
       "kind": "objects",
       "id": "linkedbranchconnection",
       "href": "/graphql/reference/objects#linkedbranchconnection",
-      "description": "<p>The connection type for LinkedBranch.</p>",
+      "description": "<p>A list of branches linked to an issue.</p>",
       "fields": [
         {
           "name": "edges",
@@ -30750,7 +30750,7 @@
       "kind": "objects",
       "id": "mannequinconnection",
       "href": "/graphql/reference/objects#mannequinconnection",
-      "description": "<p>The connection type for Mannequin.</p>",
+      "description": "<p>A list of mannequins.</p>",
       "fields": [
         {
           "name": "edges",
@@ -42408,7 +42408,7 @@
       "kind": "objects",
       "id": "organizationmemberconnection",
       "href": "/graphql/reference/objects#organizationmemberconnection",
-      "description": "<p>The connection type for User.</p>",
+      "description": "<p>A list of users who belong to the organization.</p>",
       "fields": [
         {
           "name": "edges",
@@ -63331,7 +63331,7 @@
       "kind": "objects",
       "id": "repositorymigrationconnection",
       "href": "/graphql/reference/objects#repositorymigrationconnection",
-      "description": "<p>The connection type for RepositoryMigration.</p>",
+      "description": "<p>A list of migrations.</p>",
       "fields": [
         {
           "name": "edges",
@@ -66535,7 +66535,7 @@
       "kind": "objects",
       "id": "sponsorconnection",
       "href": "/graphql/reference/objects#sponsorconnection",
-      "description": "<p>The connection type for Sponsor.</p>",
+      "description": "<p>A list of users and organizations sponsoring someone via GitHub Sponsors.</p>",
       "fields": [
         {
           "name": "edges",
@@ -67631,7 +67631,7 @@
       "kind": "objects",
       "id": "sponsorshipconnection",
       "href": "/graphql/reference/objects#sponsorshipconnection",
-      "description": "<p>The connection type for Sponsorship.</p>",
+      "description": "<p>A list of sponsorships either from the subject or received by the subject.</p>",
       "fields": [
         {
           "name": "edges",
@@ -76784,7 +76784,7 @@
       "kind": "objects",
       "id": "userconnection",
       "href": "/graphql/reference/objects#userconnection",
-      "description": "<p>The connection type for User.</p>",
+      "description": "<p>A list of users.</p>",
       "fields": [
         {
           "name": "edges",

src/graphql/data/ghec/schema.json

@@ -30510,7 +30510,7 @@
       "kind": "objects",
       "id": "linkedbranchconnection",
       "href": "/graphql/reference/objects#linkedbranchconnection",
-      "description": "<p>The connection type for LinkedBranch.</p>",
+      "description": "<p>A list of branches linked to an issue.</p>",
       "fields": [
         {
           "name": "edges",
@@ -30750,7 +30750,7 @@
       "kind": "objects",
       "id": "mannequinconnection",
       "href": "/graphql/reference/objects#mannequinconnection",
-      "description": "<p>The connection type for Mannequin.</p>",
+      "description": "<p>A list of mannequins.</p>",
       "fields": [
         {
           "name": "edges",
@@ -42408,7 +42408,7 @@
       "kind": "objects",
       "id": "organizationmemberconnection",
       "href": "/graphql/reference/objects#organizationmemberconnection",
-      "description": "<p>The connection type for User.</p>",
+      "description": "<p>A list of users who belong to the organization.</p>",
       "fields": [
         {
           "name": "edges",
@@ -63331,7 +63331,7 @@
       "kind": "objects",
       "id": "repositorymigrationconnection",
       "href": "/graphql/reference/objects#repositorymigrationconnection",
-      "description": "<p>The connection type for RepositoryMigration.</p>",
+      "description": "<p>A list of migrations.</p>",
       "fields": [
         {
           "name": "edges",
@@ -66535,7 +66535,7 @@
       "kind": "objects",
       "id": "sponsorconnection",
       "href": "/graphql/reference/objects#sponsorconnection",
-      "description": "<p>The connection type for Sponsor.</p>",
+      "description": "<p>A list of users and organizations sponsoring someone via GitHub Sponsors.</p>",
       "fields": [
         {
           "name": "edges",
@@ -67631,7 +67631,7 @@
       "kind": "objects",
       "id": "sponsorshipconnection",
       "href": "/graphql/reference/objects#sponsorshipconnection",
-      "description": "<p>The connection type for Sponsorship.</p>",
+      "description": "<p>A list of sponsorships either from the subject or received by the subject.</p>",
       "fields": [
         {
           "name": "edges",
@@ -76784,7 +76784,7 @@
       "kind": "objects",
       "id": "userconnection",
       "href": "/graphql/reference/objects#userconnection",
-      "description": "<p>The connection type for User.</p>",
+      "description": "<p>A list of users.</p>",
       "fields": [
         {
           "name": "edges",