Merge branch 'main' into hotfix/about-app-links

Author: janiceilene

.github/CODEOWNERS

@@ -1,6 +1,6 @@
 # Order is important. The LAST matching pattern has the MOST precedence.
 # gitignore style patterns are used, not globs.
-# https://help.github.com/articles/about-codeowners
+# https://docs.github.com/articles/about-codeowners
 # https://git-scm.com/docs/gitignore
 
 # Engineering

.github/ISSUE_COMMENT_TEMPLATE/target-date.yml

@@ -0,0 +1,14 @@
+---
+name: Target Date Update
+about: Target date update
+body:
+  - type: input
+    attributes:
+      name: Target completion date
+      placeholder: With context if the target completion date has changed
+      inputType: text
+  - type: input
+    attributes:
+      name: 'Attribution'
+      value: '_created with :heart: by typing_ `/status`'
+      inputType: text

.github/allowed-actions.js

@@ -39,6 +39,6 @@ module.exports = [
   "repo-sync/pull-request@33777245b1aace1a58c87a29c90321aa7a74bd7d",
   "someimportantcompany/github-actions-slack-message@0b470c14b39da4260ed9e3f9a4f1298a74ccdefd",
   "tjenkinson/gh-action-auto-merge-dependency-updates@4d7756c04d9d999c5968697a621b81c47f533d61",
-  "EndBug/add-and-commit@9358097a71ad9fb9e2f9624c6098c89193d83575",
+  "EndBug/add-and-commit@b3c7c1e078a023d75fb0bd326e02962575ce0519",
   "dorny/paths-filter@eb75a1edc117d3756a18ef89958ee59f9500ba58",
 ];

.github/workflows/build-docker-image.yml

@@ -14,7 +14,7 @@ env:
 jobs:
   build:
     # Do not run this job for translations PRs
-    if: ${{ github.ref != 'refs/heads/translations' }}
+    if: ${{ github.head_ref != 'translations' && github.ref != 'refs/heads/translations' }}
 
     runs-on: ubuntu-latest
     steps:

.github/workflows/close-external-repo-sync-prs.yml

@@ -11,7 +11,7 @@ on:
 jobs:
   invalid-repo-sync-check:
     name: Close external Repo Sync PRs
-    if: ${{ github.repository == 'github/docs' && github.ref == 'refs/heads/repo-sync' }}
+    if: ${{ github.repository == 'github/docs' && github.head_ref == 'repo-sync' }}
     runs-on: ubuntu-latest
     steps:
       - uses: actions/github-script@626af12fe9a53dc2972b48385e7fe7dec79145c9

.github/workflows/link-check-dotcom.yml

@@ -47,7 +47,7 @@ jobs:
       #   run: npm run heroku-postbuild
       #   env:
       #     DOCUBOT_REPO_PAT: ${{ secrets.DOCUBOT_REPO_PAT }}
-      #     GIT_BRANCH: ${{ github.ref }}
+      #     GIT_BRANCH: ${{ github.head_ref || github.ref }}
 
       - if: ${{ needs.see_if_should_skip.outputs.should_skip != 'true' }}
         name: Build

.github/workflows/link-check-ghae.yml

@@ -47,7 +47,7 @@ jobs:
       #   run: npm run heroku-postbuild
       #   env:
       #     DOCUBOT_REPO_PAT: ${{ secrets.DOCUBOT_REPO_PAT }}
-      #     GIT_BRANCH: ${{ github.ref }}
+      #     GIT_BRANCH: ${{ github.head_ref || github.ref }}
 
       - if: ${{ needs.see_if_should_skip.outputs.should_skip != 'true' }}
         name: Build

.github/workflows/link-check-ghes.yml

@@ -47,7 +47,7 @@ jobs:
       #   run: npm run heroku-postbuild
       #   env:
       #     DOCUBOT_REPO_PAT: ${{ secrets.DOCUBOT_REPO_PAT }}
-      #     GIT_BRANCH: ${{ github.ref }}
+      #     GIT_BRANCH: ${{ github.head_ref || github.ref }}
 
       - if: ${{ needs.see_if_should_skip.outputs.should_skip != 'true' }}
         name: Build

.github/workflows/openapi-decorate.yml

@@ -25,13 +25,10 @@ jobs:
         run: script/rest/update-files.js --decorate-only
 
       - name: Check in the decorated files
-        uses: EndBug/add-and-commit@9358097a71ad9fb9e2f9624c6098c89193d83575
+        uses: EndBug/add-and-commit@b3c7c1e078a023d75fb0bd326e02962575ce0519
         with:
           # The arguments for the `git add` command
           add: 'lib/rest/static/decorated'
 
           # The message for the commit
           message: 'Add decorated OpenAPI schema files'
-
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} # Leave this line unchanged

.github/workflows/ready-for-doc-review.yml

@@ -0,0 +1,22 @@
+name: Ready for docs-content review
+
+# **What it does**: Adds pull requests in the docs-internal repository to the docs-content first responder project board
+# **Why we have it**: So that other GitHub teams can easily request reviews from the docs-content team, and so that writers can see when a PR is ready for review
+# **Who does it impact**: Writers working in the docs-internal repository
+
+on:
+  pull_request:
+    types: [labeled]
+
+jobs:
+  request_doc_review:
+    name: Request a review from the docs-content team
+    if: github.event.label.name == 'ready-for-doc-review' && github.repository == 'github/docs-internal'
+    runs-on: ubuntu-latest
+    steps:
+      - name: Add pull request to FR project board
+        uses: rachmari/actions-add-new-issue-to-column@1a459ef92308ba7c9c9dc2fcdd72f232495574a9
+        with:
+          action-token: ${{ secrets.DOCUBOT_FR_PROJECT_BOARD_WORKFLOWS_REPO_ORG_READ_SCOPES }}
+          project-url: 'https://github.com/orgs/github/projects/1367'
+          column-name: 'Docs-internal external contributor PRs'

.github/workflows/send-eng-issues-to-backlog.yml

@@ -0,0 +1,58 @@
+name: Send Issue to How We Work Boards
+
+on:
+  issues:
+    types:
+      - labeled
+      - reopened
+
+jobs:
+  triage:
+    runs-on: ubuntu-latest
+    continue-on-error: true
+    steps:
+      - if: contains(github.event.issue.labels.*.name, 'engineering') && !contains(github.event.issue.labels.*.name, 'feature') && !contains(github.event.issue.labels.*.name, 'epic')
+        uses: actions/github-script@626af12fe9a53dc2972b48385e7fe7dec79145c9
+        with:
+          github-token: ${{ secrets.DOCUBOT_READORG_REPO_WORKFLOW_SCOPES }}
+          script: |
+            var column_id = 9659080;
+            try {
+              github.projects.createCard({
+                column_id: column_id,
+                content_id: context.payload.issue.id,
+                content_type: "Issue"
+              });
+            } catch (error) {
+              console.log(error);
+            }
+      - if: contains(github.event.issue.labels.*.name, 'engineering') && contains(github.event.issue.labels.*.name, 'feature')
+        uses: actions/github-script@626af12fe9a53dc2972b48385e7fe7dec79145c9
+        with:
+          github-token: ${{ secrets.DOCUBOT_READORG_REPO_WORKFLOW_SCOPES }}
+          script: |
+            var column_id = 13445681;
+            try {
+              github.projects.createCard({
+                column_id: column_id,
+                content_id: context.payload.issue.id,
+                content_type: "Issue"
+              });
+            } catch (error) {
+              console.log(error);
+            }
+      - if: contains(github.event.issue.labels.*.name, 'engineering') && contains(github.event.issue.labels.*.name, 'epic')
+        uses: actions/github-script@626af12fe9a53dc2972b48385e7fe7dec79145c9
+        with:
+          github-token: ${{ secrets.DOCUBOT_READORG_REPO_WORKFLOW_SCOPES }}
+          script: |
+            var column_id = 13445932;
+            try {
+              github.projects.createCard({
+                column_id: column_id,
+                content_id: context.payload.issue.id,
+                content_type: "Issue"
+              });
+            } catch (error) {
+              console.log(error);
+            }

.github/workflows/send-issues-to-how-how-we-work-boards.yml

@@ -1,4 +1,4 @@
-# NOTE: Changes to this file should also be applied to './test.yml' and './test-translations.yml'
+# NOTE: Changes to this file should also be applied to './test.yml'
 
 name: Node.js Tests - Windows
 
@@ -8,17 +8,24 @@ on:
   schedule:
     - cron: '50 19 * * *' # once a day at 19:50 UTC / 11:50 PST
 
+env:
+  CI: true
+
 jobs:
   test:
     runs-on: windows-latest
     if: (github.event_name != 'pull_request') || (github.event_name == 'pull_request' && (contains(github.event.pull_request.labels.*.name, 'Windows') || contains(github.event.pull_request.labels.*.name, 'windows')))
+    timeout-minutes: 60
     strategy:
       fail-fast: false
       matrix:
         test-group: [content, graphql, meta, rendering, routing, unit]
     steps:
       - name: Check out repo
         uses: actions/checkout@5a4ac9002d0be2fb38bd78e4b4dbde5606d7042f
+        with:
+          # Enables cloning the Early Access repo later with the relevant PAT
+          persist-credentials: 'false'
 
       - name: Setup node
         uses: actions/setup-node@c46424eee26de4078d34105d3de3cc4992202b1e
@@ -41,7 +48,15 @@ jobs:
       - name: Install dependencies
         run: npm ci
 
-      - name: Run build script
+      - if: ${{ github.repository == 'github/docs-internal' }}
+        name: Clone early access
+        run: npm run heroku-postbuild
+        env:
+          DOCUBOT_REPO_PAT: ${{ secrets.DOCUBOT_REPO_PAT }}
+          GIT_BRANCH: ${{ github.head_ref || github.ref }}
+
+      - if: ${{ github.repository != 'github/docs-internal' }}
+        name: Run build script
         run: npm run build
 
       - name: Run tests

.github/workflows/test-windows.yml

@@ -77,7 +77,7 @@ jobs:
         run: npm run heroku-postbuild
         env:
           DOCUBOT_REPO_PAT: ${{ secrets.DOCUBOT_REPO_PAT }}
-          GIT_BRANCH: ${{ github.ref }}
+          GIT_BRANCH: ${{ github.head_ref || github.ref }}
 
       - if: ${{ needs.see_if_should_skip.outputs.should_skip != 'true' && github.repository != 'github/docs-internal' }}
         name: Run build script

.github/workflows/test.yml

@@ -228,9 +228,9 @@ includeGuides:
 - Optional.
 
 ### `topics`
-- Purpose: Indicate the topics covered by the article.
-- Type: `String`
-- Optional.
+- Purpose: Indicate the topics covered by the article. The topics are used to filter guides on some landing pages. For example, the guides at the bottom of [this page](https://docs.github.com/en/actions/guides) can be filtered by topics and the topics are listed under the guide intro. Topics are also added to all search records that get created for each page. The search records contain a `topics` property that is used to filter search results by topics. For more information, see the [Search](/contributing/search.md) contributing guide. Refer to the content models for more details around adding topics. A full list of  existing topics is located in the [allowed topics file](/data/allowed-topics.js). If topics in article frontmatter and the allow-topics list become out of sync, the [topics CI test](/tests/unit/search/topics.js) will fail.
+- Type: Array of `String`s
+- Optional: Topics are preferred for each article, but, there may be cases where existing articles don't yet have topics or a adding a topic to a new article may not add value.
 
 ### `contributor`
 - Purpose: Indicate an article is contributed and maintained by a third-party organization, typically a GitHub Technology Partner.

assets/images/help/billing/ghas-seats-org.png

@@ -0,0 +1,68 @@
+---
+title: Adding labels to issues
+intro: You can use {% data variables.product.prodname_actions %} to automatically label issues.
+product: '{% data reusables.gated-features.actions %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+type: 'tutorial'
+topics:
+  - 'Workflows'
+  - 'Project management'
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
+{% data reusables.actions.ae-self-hosted-runners-notice %}
+
+### Introduction
+
+This tutorial demonstrates how to use the [`andymckay/labeler` action](https://github.com/marketplace/actions/simple-issue-labeler) in a workflow to label newly opened or reopened issues. For example, you can add the `triage` label every time an issue is opened or reopened. Then, you can see all issues that need to be triaged by filtering for issues with the `triage` label.
+
+In the tutorial, you will first make a workflow file that uses the [`andymckay/labeler` action](https://github.com/marketplace/actions/simple-issue-labeler). Then, you will customize the workflow to suit your needs.
+
+### Creating the workflow
+
+1. {% data reusables.actions.choose-repo %}
+2. {% data reusables.actions.make-workflow-file %}
+3. Copy the following YAML contents into your workflow file.
+
+    {% raw %}
+    ```yaml{:copy}
+    name: Label issues
+    on:
+      issues:
+        types:
+          - reopened
+          - opened
+    jobs:
+      label_issues:
+        runs-on: ubuntu-latest
+        steps:
+          - name: Label issues
+            uses: andymckay/[email protected]
+            with:
+              add-labels: "triage"
+    ```
+    {% endraw %}
+4. Customize the parameters in your workflow file:
+   - Change the value for `add-labels` to the list of labels that you want to add to the issue. Separate multiple labels with commas. For example, `"help wanted, good first issue"`. For more information about labels, see "[Managing labels](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)."
+5. {% data reusables.actions.commit-workflow %}
+
+### Testing the workflow
+
+Every time an issue in your repository is opened or reopened, this workflow will add the labels that you specified to the issue.
+
+Test out your workflow by creating an issue in your repository.
+
+1. Create an issue in your repository. For more information, see "[Creating an issue](/github/managing-your-work-on-github/creating-an-issue)."
+2. To see the workflow run that was triggered by creating the issue, view the history of your workflow runs. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
+3. When the workflow completes, the issue that you created should have the specified labels added.
+
+### Next steps
+
+- To learn more about additional things you can do with the `andymckay/labeler` action, like removing labels or skipping this action if the issue is assigned or has a specific label, see the [`andymckay/labeler` action documentation](https://github.com/marketplace/actions/simple-issue-labeler).
+- To learn more about different events that can trigger your workflow, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#issues)." The `andymckay/labeler` action only works on `issues`, `pull_request`, or `project_card` events.
+- [Search GitHub](https://github.com/search?q=%22uses:+andymckay/labeler%22&type=code) for examples of workflows using this action.