Merge branch 'main' into update-autofix-docs-python-support

Author: saritai

.github/workflows/content-linter-rules-docs.yml

@@ -0,0 +1,48 @@
+name: 'Check content-linter rules docs'
+
+# **What it does**: Makes sure the content-linter-rules.md is up-to-date.
+# **Why we have it**: So what's automated doesn't fall behind
+# **Who does it impact**: Docs content.
+
+on:
+  workflow_dispatch:
+  pull_request:
+    paths:
+      - 'src/content-linter/**'
+      # In case imported markdownlint rules are updated
+      - package-lock.json
+      # In case manual changes are made to the content-linter-rules.md file
+      - data/reusables/contributing/content-linter-rules.md
+      # Self-test
+      - .github/workflows/content-linter-rules-docs.yml
+
+permissions:
+  contents: read
+
+jobs:
+  check-content-linter-rules-docs:
+    runs-on: ${{ fromJSON('["ubuntu-latest", "ubuntu-20.04-xl"]')[github.repository == 'github/docs-internal'] }}
+    if: github.repository == 'github/docs-internal' || github.repository == 'github/docs'
+    steps:
+      - name: Checkout
+        uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
+
+      - uses: ./.github/actions/node-npm-setup
+
+      - name: Check that content-linter-rules.md is up-to-date
+        run: npm run generate-content-linter-docs
+
+      - name: Fail if it isn't up-to-date
+        run: |
+          if [ -n "$(git status --porcelain)" ]; then
+            git status
+            git diff
+
+            # Some whitespace for the sake of the message below
+            echo ""
+            echo ""
+
+            echo "content-linter-rules.md is out of date."
+            echo "Please run 'npm run generate-content-linter-docs' and commit the changes."
+            exit 1;
+          fi

assets/images/help/organizations/sidebar-repository-rule-insights.png

@@ -58,7 +58,7 @@ In the event that user access tokens are compromised, you should immediately rev
 
 Your OAuth app can be accessed by users outside your organization or enterprise. If you intend an app to be used only by members of your organization or enterprise, you should check the user's membership status when the user signs in to your app.
 
-To find the list of organizations a user is a member of, you can use the "List organizations for the authenticated user" endpoint. Then you can validate this list against a list of approved organizations for your app. For more information, see "[AUTOTITLE](/rest/orgs/orgs#list-organizations-for-the-authenticated-user)" in the REST API documentation.
+To find the list of organizations a user is a member of, you can use the "List organizations for the authenticated user" endpoint. Then you can validate this list against a list of approved organizations for your app. For more information, see "[AUTOTITLE](/rest/orgs/orgs#list-organizations-for-the-authenticated-user)."
 
 {% data reusables.emus.oauth-app-note %}
 

assets/images/help/organizations/sidebar-repository-rulesets.png

@@ -36,7 +36,7 @@ Anyone can install {% data variables.product.prodname_github_apps %} on their pe
 
 Organization owners can install {% data variables.product.prodname_github_apps %} on their organization.
 
-Admins of repositories that are owned by an organization can also install {% data variables.product.prodname_github_apps %} on the organization if they only grant the app access to repositories that they are an admin of and if the app does not request any organization resources. Organization owners can prevent outside collaborators who are repository admins from installing {% data variables.product.prodname_github_apps %}.
+Admins of repositories that are owned by an organization can also install {% data variables.product.prodname_github_apps %} on the organization if they only grant the app access to repositories that they are an admin of and if the app does not request any organization permissions or the "repository administration" permission. Organization owners can prevent outside collaborators who are repository admins from installing {% data variables.product.prodname_github_apps %}.
 
 Organization members who are not organization owners or repository admins can still select the organization during the install process. Instead of installing the app, {% data variables.product.company_short %} will send a notification to the organization owner to request the organization owner to install the app.
 

content/apps/oauth-apps/building-oauth-apps/best-practices-for-creating-an-oauth-app.md

@@ -44,7 +44,7 @@ Organization owners can install {% data variables.product.prodname_github_apps %
 
 For enterprises that pay by credit card, enterprise owners who are also organization owners can install {% data variables.product.prodname_github_apps %} on organizations within their enterprise.
 
-Admins of repositories that are owned by an organization can also install {% data variables.product.prodname_github_apps %} on the organization if they only grant the app access to repositories that they are an admin of and if the app does not request any organization resources. Organization owners can prevent outside collaborators who are repository admins from installing {% data variables.product.prodname_github_apps %}.
+Admins of repositories that are owned by an organization can also install {% data variables.product.prodname_github_apps %} on the organization if they only grant the app access to repositories that they are an admin of and if the app does not request any organization permissions or the "repository administration" permission. Organization owners can prevent outside collaborators who are repository admins from installing {% data variables.product.prodname_github_apps %}.
 
 The "app manager" role in an organization does not give a person the ability to install a {% data variables.product.prodname_github_app %} in the organization. For more information, see "[AUTOTITLE](/apps/maintaining-github-apps/about-github-app-managers)."
 

content/apps/using-github-apps/installing-a-github-app-from-a-third-party.md

@@ -114,7 +114,7 @@ For a real-world example, see "[Example mutation](#example-mutation)."
 
 ## Working with variables
 
-[Variables](https://graphql.github.io/learn/queries/#variables) can make queries more dynamic and powerful, and they can reduce complexity when passing mutation input objects.
+[Variables](https://graphql.org/learn/queries/#variables) can make queries more dynamic and powerful, and they can reduce complexity when passing mutation input objects.
 
 {% note %}
 
@@ -398,7 +398,7 @@ You may notice that the `content` field value in the earlier example (where it's
 - When you use `content` directly in the mutation, the schema expects the value to be of type [`ReactionContent`](/graphql/reference/enums#reactioncontent), which is an _enum_, not a string. Schema validation will throw an error if you add quotes around the enum value, as quotes are reserved for strings.
 - When you use `content` in a variable, the variables section must be valid JSON, so the quotes are required. Schema validation correctly interprets the `ReactionContent` type when the variable is passed into the mutation during execution.
 
-For more information on the difference between enums and strings, see the [official GraphQL spec](https://graphql.github.io/graphql-spec/June2018/#sec-Enums).
+For more information on the difference between enums and strings, see the [official GraphQL spec](https://spec.graphql.org/June2018/#sec-Enums).
 
 {% endnote %}
 

content/apps/using-github-apps/installing-a-github-app-from-github-marketplace-for-your-organizations.md

@@ -18,14 +18,14 @@ The GitHub GraphQL API represents an architectural and conceptual shift from the
 
 ## Schema
 
-A schema defines a GraphQL API's type system. It describes the complete set of possible data (objects, fields, relationships, everything) that a client can access. Calls from the client are [validated](https://graphql.github.io/learn/validation/) and [executed](https://graphql.github.io/learn/execution/) against the schema. A client can find information about the schema via [introspection](#discovering-the-graphql-api). A schema resides on the GraphQL API server. For more information, see "[Discovering the GraphQL API](#discovering-the-graphql-api)."
+A schema defines a GraphQL API's type system. It describes the complete set of possible data (objects, fields, relationships, everything) that a client can access. Calls from the client are [validated](https://graphql.org/learn/validation/) and [executed](https://graphql.org/learn/execution/) against the schema. A client can find information about the schema via [introspection](#discovering-the-graphql-api). A schema resides on the GraphQL API server. For more information, see "[Discovering the GraphQL API](#discovering-the-graphql-api)."
 
 ## Field
 
-A field is a unit of data you can retrieve from an object. As the [official GraphQL docs](https://graphql.github.io/learn/schema/) say:
+A field is a unit of data you can retrieve from an object. As the [official GraphQL docs](https://graphql.org/learn/schema/) say:
 "The GraphQL query language is basically about selecting fields on objects."
 
-The [official spec](https://graphql.github.io/graphql-spec/June2018/#sec-Language.Fields) also says about fields:
+The [official spec](https://spec.graphql.org/June2018/#sec-Language.Fields) also says about fields:
 
 > All GraphQL operations must specify their selections down to fields which return scalar values to ensure an unambiguously shaped response.
 
@@ -78,7 +78,7 @@ _Node_ is a generic term for an object. You can look up a node directly, or you
 
 ## Discovering the GraphQL API
 
-GraphQL is [introspective](https://graphql.github.io/learn/introspection/). This means you can query a GraphQL schema for details about itself.
+GraphQL is [introspective](https://graphql.org/learn/introspection/). This means you can query a GraphQL schema for details about itself.
 
 - Query `__schema` to list all types defined in the schema and get details about each:
 

content/graphql/guides/forming-calls-with-graphql.md

@@ -21,7 +21,7 @@ Migrating from REST to GraphQL represents a significant shift in API logic. The
 
 To migrate your code from the [REST API](/rest) to the GraphQL API:
 
-- Review the [GraphQL spec](https://graphql.github.io/graphql-spec/June2018/)
+- Review the [GraphQL spec](https://spec.graphql.org/June2018/)
 - Review GitHub's [GraphQL schema](/graphql/reference)
 - Consider how any existing code you have currently interacts with the GitHub REST API
 - Use [Global Node IDs](/graphql/guides/using-global-node-ids) to reference objects between API versions

content/graphql/guides/introduction-to-graphql.md

@@ -107,7 +107,7 @@ When you run this query, you'll see that the `__typename` is [`User`](/graphql/r
 
 ## 3. Do a direct node lookup in GraphQL
 
-Once you've confirmed the type, you can use an [inline fragment](https://graphql.github.io/learn/queries/#inline-fragments) to access the object by its ID and return additional data. In this example, we define the fields on `User` that we'd like to query:
+Once you've confirmed the type, you can use an [inline fragment](https://graphql.org/learn/queries/#inline-fragments) to access the object by its ID and return additional data. In this example, we define the fields on `User` that we'd like to query:
 
 ```graphql
 query {