Merge branch 'main' into patch-2

Author: lecoursen

.github/ISSUE_TEMPLATE/improve-existing-docs.md

@@ -0,0 +1,46 @@
+name: Improve existing content
+description: Make a suggestion to improve the content in an existing article
+labels:
+  - content
+body:
+  - type: markdown
+    attributes:
+      value: |
+        **HUBBERS:** This is the github/docs open source repo. You may want to open an issue in the internal-only github/docs-content repo instead.
+
+        * For questions, ask in [Discussions](https://github.com/github/docs/discussions)
+        * Before you file an issue read the [Contributing guide](https://github.com/github/docs/blob/main/CONTRIBUTING.md)
+        * Check to make sure someone hasn't already opened a similar [issue](https://github.com/github/docs/issues)
+
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: This project has a [Code of Conduct](https://github.com/github/docs/blob/main/CODE_OF_CONDUCT.md) that all participants are expected to understand and follow.
+      options:
+        - label: I have read and agree to the GitHub Docs project's Code of Conduct.
+          required: true
+
+  - type: textarea
+    attributes:
+      label: What article on docs.github.com is affected?
+      description: Please link to the article you'd like to see updated.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: What part(s) of the article would you like to see updated?
+      description: |
+        - Give as much detail as you can to help us understand the change you want to see. 
+        - Why should the docs be changed? What use cases does it support? 
+        - What is the expected outcome?
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Additional information
+      description: Add any other context or screenshots about the feature request here.
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/improve-existing-docs.yaml

@@ -0,0 +1,47 @@
+name: Improve the docs.github.com site
+description: Make a suggestion or report a problem about the technical implementation of docs.github.com.
+labels:
+  - content
+body:
+  - type: markdown
+    attributes:
+      value: |
+        **HUBBERS!! THIS IS GITHUB/DOCS OPEN SOURCE REPO. OPEN AN ISSUE IN GITHUB/DOCS-CONTENT INSTEAD.**
+
+        * For questions, ask in [Discussions](https://github.com/github/docs/discussions)
+        * Before you file an issue read the [Contributing guide](https://github.com/github/docs/blob/main/CONTRIBUTING.md)
+        * Check to make sure someone hasn't already opened a similar [issue](https://github.com/github/docs/issues)
+
+  - type: checkboxes
+    attributes:
+      label: Code of Conduct
+      description: By submitting this issue, you agree to follow our [Code of Conduct](https://example.com)
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true
+
+  - type: textarea
+    attributes:
+      label: What article on docs.github.com is affected?
+      description: |
+        Include links to articles where you're seeing a problem, screenshots, what browser you're using, etc.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: What changes are you suggesting?
+      description: |
+        - Give as much detail as you can to help us understand the change you want to see. 
+        - Why should the docs be changed? What use cases does it support? 
+        - What is the expected outcome?
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Additional information
+      description: |
+        Any additional information, configuration, or data that might be necessary to reproduce the issue.
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/improve-the-site.md

@@ -102,7 +102,7 @@ We cannot accept contributions to the [REST API reference documentation](https:/
 ### :question: Support
 We are a small team working hard to keep up with the documentation demands of a continuously changing product. Unfortunately, we just can't help with support questions in this repository. If you are experiencing a problem with GitHub, unrelated to our documentation, please [contact GitHub Support directly](https://support.github.com/contact). Any issues, discussions, or pull requests opened here requesting support will be given information about how to contact GitHub Support, then closed and locked.
 
-If you're having trouble with your GitHub account, contact [Support](https://support.github.com/contact).
+If you're having trouble with your GitHub account, contact [Support](https://support.github.com/contact?tags=docs-contributing-guide).
 
 ### :earth_asia: Translations
 

.github/ISSUE_TEMPLATE/improve-the-site.yml

@@ -14,7 +14,10 @@ export const GuideCard = ({ guide }: Props) => {
         href={guide.href}
       >
         <h2 dangerouslySetInnerHTML={{ __html: guide.title }} />
-        <p className="mt-2 mb-4 color-text-tertiary">{guide.intro}</p>
+        <p
+          className="mt-2 mb-4 color-text-tertiary"
+          dangerouslySetInnerHTML={{ __html: guide.intro || '' }}
+        />
 
         <footer className="d-flex">
           <div className="mr-1">

CONTRIBUTING.md

@@ -52,7 +52,7 @@ export const LearningTrack = ({ track }: Props) => {
                   </span>
                 )}
               </div>
-              <h5 className="flex-auto pr-2">{guide.title}</h5>
+              <h5 className="flex-auto pr-2" dangerouslySetInnerHTML={{ __html: guide.title }} />
               <div className="color-text-tertiary h6 text-uppercase flex-shrink-0">
                 {t('guide_types')[guide.page?.type || '']}
               </div>

assets/images/enterprise/2.22/management-console/abuse-rate-limits-checkbox.png

@@ -30,9 +30,10 @@ export const SubLandingHero = () => {
           </div>
         </div>
         <h3 className="font-mktg h3-mktg my-4 color-text-primary">{guide.title}</h3>
-        <div className="lead-mktg color-text-secondary f5 my-4 truncate-overflow-8">
-          {guide.intro}
-        </div>
+        <div
+          className="lead-mktg color-text-secondary f5 my-4 truncate-overflow-8"
+          dangerouslySetInnerHTML={{ __html: guide.intro }}
+        />
       </Link>
     </li>
   ))

assets/images/enterprise/3.0/management-console/abuse-rate-limits-checkbox.png

@@ -108,7 +108,7 @@ See [`contributing/redirects`](contributing/redirects.md) for more info.
 
 ### `shortTitle`
 
-- Purpose: An abbreviated variant of the page title for use in breadcrumbs.
+- Purpose: An abbreviated variant of the page title for use in breadcrumbs and navigation elements.
 - Type: `String`
 - Optional. If omitted, `title` will be used.
 

assets/images/enterprise/3.1/management-console/abuse-rate-limits-checkbox.png

@@ -71,7 +71,7 @@ Based on the `schedule` parameter (for example, every day at 1:30 UTC), your wor
 
 You can view the history of your workflow runs to see this workflow run periodically. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
 
-This workflow will only label and/or close 30 issues at a time in order to avoid rate limit abuse. You can configure this with the `operations-per-run` setting. For more information, see the [`actions/stale` action documentation](https://github.com/marketplace/actions/close-stale-issues).
+This workflow will only label and/or close 30 issues at a time in order to avoid exceeding a rate limit. You can configure this with the `operations-per-run` setting. For more information, see the [`actions/stale` action documentation](https://github.com/marketplace/actions/close-stale-issues).
 
 ## Next steps
 

assets/images/enterprise/management-console/api-rate-limits-checkbox.png

@@ -79,7 +79,8 @@ This procedure demonstrates how to create the service account for your GKE integ
   $ gcloud projects add-iam-policy-binding $GKE_PROJECT \
     --member=serviceAccount:$SA_EMAIL \
     --role=roles/container.admin \
-    --role=roles/storage.admin
+    --role=roles/storage.admin \
+    --role=roles/container.clusterViewer
   ```
   {% endraw %}
 1. Download the JSON keyfile for the service account:
@@ -88,7 +89,7 @@ This procedure demonstrates how to create the service account for your GKE integ
   $ gcloud iam service-accounts keys create key.json --iam-account=$SA_EMAIL
   ```
   {% endraw %}
-1. Store the project ID as a secret named `GKE_PROJECT`:
+1. Store the service account key as a secret named `GKE_SA_KEY`:
   {% raw %}
   ```
   $ export GKE_SA_KEY=$(cat key.json | base64)

assets/images/enterprise/management-console/git-rate-limits-checkbox.png

@@ -131,7 +131,7 @@ The `build-push-action` options required for {% data variables.product.prodname_
 {% ifversion fpt %}
 {% data reusables.package_registry.publish-docker-image %}
 
-The above workflow if triggered by a push to the "release" branch. It checks out the GitHub repository, and uses the `login-action` to log in to the {% data variables.product.prodname_container_registry %}. It then extracts labels and tags for the Docker image. Finally, it and uses the `build-push-action` action to build the image and publish it on the {% data variables.product.prodname_container_registry %}.
+The above workflow if triggered by a push to the "release" branch. It checks out the GitHub repository, and uses the `login-action` to log in to the {% data variables.product.prodname_container_registry %}. It then extracts labels and tags for the Docker image. Finally, it uses the `build-push-action` action to build the image and publish it on the {% data variables.product.prodname_container_registry %}.
 
 {% else %}
 ```yaml{:copy}

assets/images/enterprise/management-console/secondary-rate-limits-checkbox.png

@@ -143,7 +143,7 @@ For more information, see "[Using databases and service containers](/actions/con
 
 ## Using labels to route workflows
 
-This feature helps you assign jobs to a specific hosted runner. If you want to be sure that a particular type of runner will process your job, you can use labels to control where jobs are executed. You can assign labels to a hosted runner, and then refer to these labels in your YAML workflow, ensuring that the job is routed in a predictable way.
+This feature helps you assign jobs to a specific hosted runner. If you want to be sure that a particular type of runner will process your job, you can use labels to control where jobs are executed. You can assign labels to a self-hosted runner in addition to their default label of `self-hosted`. Then, you can refer to these labels in your YAML workflow, ensuring that the job is routed in a predictable way.{% ifversion not ghae %} {% data variables.product.prodname_dotcom %}-hosted runners have predefined labels assigned.{% endif %}
 
 {% ifversion ghae %}
 This example shows how a workflow can use labels to specify the required runner:
@@ -156,13 +156,18 @@ jobs:
 
 For more information, see ["Using labels with {% data variables.actions.hosted_runner %}](/actions/using-github-hosted-runners/using-labels-with-ae-hosted-runners)."
 {% else %}
+This example shows how a workflow can use labels to specify the required runner:
+
 ```yaml
 jobs:
   example-job:
     runs-on: [self-hosted, linux, x64, gpu]
 ```
 
-For more information, see ["Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)."
+A workflow will only run on a runner that has all the labels in the `runs-on` array. The job will preferentially go to an idle self-hosted runner with the specified labels. If none are available and a {% data variables.product.prodname_dotcom %}-hosted runner with the specified labels exists, the job will go to a {% data variables.product.prodname_dotcom %}-hosted runner.
+
+To learn more about self-hosted runner labels, see ["Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)."
+To learn more about {% data variables.product.prodname_dotcom %}-hosted runner labels, see ["Supported runners and hardware resources"](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources).
 {% endif %}
 
 {% ifversion fpt or ghes > 3.0 %}