[pull] main from github:main

.devcontainer/library-scripts/github-debian.sh

@@ -4,7 +4,7 @@
 # Licensed under the MIT License. See https://go.microsoft.com/fwlink/?linkid=2090316 for license information.
 #-------------------------------------------------------------------------------------------------------------
 #
-# Docs: https://github.com/microsoft/vscode-dev-containers/blob/master/script-library/docs/github.md
+# Docs: https://github.com/microsoft/vscode-dev-containers/blob/main/script-library/docs/github-cli.md
 #
 # Syntax: ./github-debian.sh [version]
 

.github/actions/setup-elasticsearch/action.yml

@@ -17,7 +17,7 @@ runs:
       with:
         # Make sure this matches production
         # It might also need to match what's available on Docker hub
-        elasticsearch version: '8.8.2'
+        elasticsearch version: '8.12.0'
         host port: 9200
         container port: 9200
         host node port: 9300

.github/workflows/content-lint-markdown.yml

@@ -32,10 +32,19 @@ jobs:
         id: changed-files
         uses: tj-actions/changed-files@716b1e13042866565e00e85fd4ec490e186c4a2f # v41.0.1
         with:
+          # No need to escape the file names because we make the output of
+          # tj-actions/changed-files be set as an environment variable. Not
+          # as a direct input to the line of bash that uses it.
+          safe_output: false
           files: |
             content/**
             data/**
 
       - name: Run content linter if changed content/data files
         if: steps.changed-files.outputs.any_changed == 'true'
-        run: npm run lint-content -- --errors-only --paths ${{ steps.changed-files.outputs.all_changed_files }}
+        env:
+          # Make it an environment variable so that its value doesn't need to be escaped.
+          # See https://docs.github.com/en/actions/security-guides/security-hardening-for-github-actions#using-an-intermediate-environment-variable
+          CHANGED_FILES: |-
+            ${{ steps.changed-files.outputs.all_changed_files }}
+        run: npm run lint-content -- --errors-only --paths "$CHANGED_FILES"

.github/workflows/sync-search-pr.yml

@@ -13,6 +13,8 @@ on:
       - 'package*.json'
       # Ultimately, for debugging this workflow itself
       - .github/workflows/sync-search-pr.yml
+      # Make sure we run this if the composite action changes
+      - .github/actions/setup-elasticsearch/action.yml
 
 permissions:
   contents: read

.github/workflows/test-changed-content.yml

@@ -47,6 +47,11 @@ jobs:
         id: changed-files
         uses: tj-actions/changed-files@716b1e13042866565e00e85fd4ec490e186c4a2f # v41.0.1
         with:
+          # No need to escape the file names because we make the output of
+          # tj-actions/changed-files be set as an environment variable. Not
+          # as a direct input to the line of bash that uses it.
+          # See https://docs.github.com/en/actions/security-guides/security-hardening-for-github-actions#using-an-intermediate-environment-variable
+          safe_output: false
           files: 'content/**'
           # Necessary so we can know what the old name was when a
           # content file was renamed.

content/account-and-profile/index.md

@@ -17,7 +17,7 @@ featuredLinks:
     - /account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile
     - /account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox
     - /account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address
-    - '{% ifversion ghes or ghae %}/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories{% endif %}'
+    - '{% ifversion ghes %}/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories{% endif %}'
 changelog:
   label: 'profiles, github-themes, notifications'
   versions:

content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/verifying-your-email-address.md

@@ -27,7 +27,7 @@ If you do not verify your email address, you will not be able to:
 - Generate {% data variables.product.pat_generic %}s
 - Receive email notifications
 - Star repositories
-- Create or update project boards, including adding cards
+- Create or update projects
 - Create or update gists
 - Create or use {% data variables.product.prodname_actions %}
 - Sponsor developers with {% data variables.product.prodname_sponsors %}

content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-user-account-settings/about-your-personal-dashboard.md

@@ -44,7 +44,7 @@ In the left sidebar of your dashboard, you can access the top repositories and t
 
 The list of top repositories is automatically generated, and can include any repository you have interacted with, whether it's owned directly by your account or not. Interactions include making commits and opening or commenting on issues and pull requests. The list of top repositories cannot be edited, but repositories will drop off the list 1 year after you last interacted with them.
 
-You can also find a list of your recently visited repositories, teams, and project boards when you click into the search bar at the top of any page on {% data variables.product.product_name %}.
+You can also find a list of your recently visited repositories, teams, and projects when you click into the search bar at the top of any page on {% data variables.product.product_name %}.
 
 ## Staying updated with activity from the community
 

content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-user-account-settings/managing-access-to-your-personal-accounts-project-boards.md

@@ -1,6 +1,6 @@
 ---
-title: Managing access to your personal account's project boards
-intro: 'As a project board owner, you can add or remove a collaborator and customize their permissions to a project board.'
+title: 'Managing access to your personal account''s {% data variables.projects.projects_v1_boards %}'
+intro: 'As a {% data variables.projects.projects_v1_board %} owner, you can add or remove a collaborator and customize their permissions to a {% data variables.projects.projects_v1_board %}.'
 redirect_from:
   - /articles/managing-project-boards-in-your-repository-or-organization
   - /articles/managing-access-to-your-user-account-s-project-boards
@@ -16,21 +16,22 @@ versions:
   ghec: '*'
 topics:
   - Accounts
-shortTitle: Manage access project boards
+shortTitle: 'Manage {% data variables.projects.projects_v1_boards %} access'
+allowTitleToDifferFromFilename: true
 ---
-A collaborator is a person who has permissions to a project board you own. A collaborator's permissions will default to read access. For more information, see "[AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-user-account-settings/permission-levels-for-a-project-board-owned-by-a-personal-account)."
+A collaborator is a person who has permissions to a {% data variables.projects.projects_v1_board %} you own. A collaborator's permissions will default to read access. For more information, see "[AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-user-account-settings/permission-levels-for-a-project-board-owned-by-a-personal-account)."
 
-## Inviting collaborators to a user-owned project board
+## Inviting collaborators to a user-owned {% data variables.projects.projects_v1_board %}
 
-1. Navigate to the project board where you want to add an collaborator.
+1. Navigate to the {% data variables.projects.projects_v1_board %} where you want to add an collaborator.
 {% data reusables.project-management.click-menu %}
 {% data reusables.project-management.access-collaboration-settings %}
 {% data reusables.project-management.collaborator-option %}
 1. Under "Search by username, full name or email address", type the collaborator's name, username, or {% data variables.product.prodname_dotcom %} email.
 {% data reusables.project-management.add-collaborator %}
 1. The new collaborator has read permissions by default. Optionally, next to the new collaborator's name, use the drop-down menu and choose a different permission level.
 
-## Removing a collaborator from a user-owned project board
+## Removing a collaborator from a user-owned {% data variables.projects.projects_v1_board %}
 
 {% data reusables.project-management.click-menu %}
 {% data reusables.project-management.access-collaboration-settings %}

content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-user-account-settings/permission-levels-for-a-project-board-owned-by-a-personal-account.md

@@ -1,6 +1,6 @@
 ---
-title: Permission levels for a project board owned by a personal account
-intro: 'A project board owned by a personal account has two permission levels: the project board owner and collaborators.'
+title: 'Permission levels for a {% data variables.projects.projects_v1_board %} owned by a personal account'
+intro: 'A {% data variables.projects.projects_v1_board %} owned by a personal account has two permission levels: the {% data variables.projects.projects_v1_board %} owner and collaborators.'
 redirect_from:
   - /articles/permission-levels-for-user-owned-project-boards
   - /github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards
@@ -13,51 +13,52 @@ versions:
   ghec: '*'
 topics:
   - Accounts
-shortTitle: Project board permissions
+shortTitle: '{% data variables.projects.projects_v1_board_caps %} permissions'
+allowTitleToDifferFromFilename: true
 ---
 ## Permissions overview
 
-There is only one owner of a user-owned project board; this permission cannot be shared with another personal account. In addition to the owner, other people can collaborate on project boards.
+There is only one owner of a user-owned {% data variables.projects.projects_v1_board %}; this permission cannot be shared with another personal account. In addition to the owner, other people can collaborate on {% data variables.projects.projects_v1_boards %}.
 
-There are three levels of permissions for project board collaborators:
+There are three levels of permissions for {% data variables.projects.projects_v1_board %} collaborators:
 
 {% data reusables.project-management.project-board-permissions %}
 
-## Owner and admin permissions for a user-owned project board
+## Owner and admin permissions for a user-owned {% data variables.projects.projects_v1_board %}
 
-The project board owner and collaborators with admin access have full control of the project board. In addition to all the permissions allowed by project board collaborators, a project board owner and collaborator with admin access can:
+The {% data variables.projects.projects_v1_board %} owner and collaborators with admin access have full control of the {% data variables.projects.projects_v1_board %}. In addition to all the permissions allowed by {% data variables.projects.projects_v1_board %} collaborators, a {% data variables.projects.projects_v1_board %} owner and collaborator with admin access can:
 
-- [Manage, view, and add collaborators](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-user-account-settings/managing-access-to-your-personal-accounts-project-boards)
-- [Configure a project board as public or private](/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility)
-- [Delete a project board](/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board)
-- [Close a project board](/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board)
-- [Reopen a closed project board](/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board)
+- [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-user-account-settings/managing-access-to-your-personal-accounts-project-boards)
+- [AUTOTITLE](/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility)
+- [AUTOTITLE](/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board)
+- [AUTOTITLE](/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board)
+- [AUTOTITLE](/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board)
 
-## Read and write permissions for a user-owned project board
+## Read and write permissions for a user-owned {% data variables.projects.projects_v1_board %}
 
-Collaborators with read access to a user-owned project board can:
+Collaborators with read access to a user-owned {% data variables.projects.projects_v1_board %} can:
 
-- View a project board
-- Copy a project board
-- Filter cards on a project board
+- View a {% data variables.projects.projects_v1_board %}
+- Copy a {% data variables.projects.projects_v1_board %}
+- Filter cards on a {% data variables.projects.projects_v1_board %}
 
-Collaborators with write access to a user-owned project board can:
+Collaborators with write access to a user-owned {% data variables.projects.projects_v1_board %} can:
 
-- View a project board
-- Copy a project board
-- Filter cards on a project board
-- Edit a project board
-- Link a repository to a project board
-- Configure automation for project boards
-- Copy a project board
-- Add issues and pull requests to a project board
-- Add notes to a project board
-- Track progress on your project board
-- Archive cards on a project board
+- View a {% data variables.projects.projects_v1_board %}
+- Copy a {% data variables.projects.projects_v1_board %}
+- Filter cards on a {% data variables.projects.projects_v1_board %}
+- Edit a {% data variables.projects.projects_v1_board %}
+- Link a repository to a {% data variables.projects.projects_v1_board %}
+- Configure automation for {% data variables.projects.projects_v1_boards %}
+- Copy a {% data variables.projects.projects_v1_board %}
+- Add issues and pull requests to a {% data variables.projects.projects_v1_board %}
+- Add notes to a {% data variables.projects.projects_v1_board %}
+- Track progress on your {% data variables.projects.projects_v1_board %}
+- Archive cards on a {% data variables.projects.projects_v1_board %}
 
-## Project board visibility
+## {% data variables.projects.projects_v1_board_caps %} visibility
 
-You can change the project board's visibility from private to public and back again. By default, user-owned project boards are private. For more information, see "[AUTOTITLE](/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility)."
+You can change the {% data variables.projects.projects_v1_board %}'s visibility from private to {% ifversion ghae %}internal{% else %}public{% endif %} and back again. By default, user-owned {% data variables.projects.projects_v1_boards %} are private. For more information, see "[AUTOTITLE](/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility)."
 
 ## Further reading
 

content/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners.md

@@ -12,7 +12,7 @@ versions:
   ghec: '*'
 type: overview
 ---
- 
+
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
 ## About self-hosted runners
@@ -232,7 +232,7 @@ You can also use self-hosted runners with a proxy server. For more information,
 
 For more information about troubleshooting common network connectivity issues, see "[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/monitoring-and-troubleshooting-self-hosted-runners#troubleshooting-network-connectivity)."
 
-{% ifversion ghes or ghae %}
+{% ifversion ghes %}
 
 ## Communication between self-hosted runners and {% data variables.product.prodname_dotcom_the_website %}
 

content/actions/learn-github-actions/understanding-github-actions.md

@@ -82,7 +82,7 @@ For more information, see "[AUTOTITLE](/actions/creating-actions)."
 
 ### Runners
 
-{% data reusables.actions.about-runners %} Each runner can run a single job at a time. {% ifversion ghes or ghae %} You must host your own runners for {% data variables.product.product_name %}. {% elsif fpt or ghec %}{% data variables.product.company_short %} provides Ubuntu Linux, Microsoft Windows, and macOS runners to run your workflows; each workflow run executes in a fresh, newly-provisioned virtual machine. {% ifversion actions-hosted-runners %} {% data variables.product.prodname_dotcom %} also offers {% data variables.actions.hosted_runner %}s, which are available in larger configurations. For more information, see "[AUTOTITLE](/actions/using-github-hosted-runners/using-larger-runners)." {% endif %}If you need a different operating system or require a specific hardware configuration, you can host your own runners.{% endif %} For more information{% ifversion fpt or ghec %} about self-hosted runners{% endif %}, see "[AUTOTITLE](/actions/hosting-your-own-runners)."
+{% data reusables.actions.about-runners %} Each runner can run a single job at a time. {% ifversion ghes %} You must host your own runners for {% data variables.product.product_name %}. {% elsif fpt or ghec %}{% data variables.product.company_short %} provides Ubuntu Linux, Microsoft Windows, and macOS runners to run your workflows; each workflow run executes in a fresh, newly-provisioned virtual machine. {% ifversion actions-hosted-runners %} {% data variables.product.prodname_dotcom %} also offers {% data variables.actions.hosted_runner %}s, which are available in larger configurations. For more information, see "[AUTOTITLE](/actions/using-github-hosted-runners/using-larger-runners)." {% endif %}If you need a different operating system or require a specific hardware configuration, you can host your own runners.{% endif %} For more information{% ifversion fpt or ghec %} about self-hosted runners{% endif %}, see "[AUTOTITLE](/actions/hosting-your-own-runners)."
 
 {% data reusables.actions.workflow-basic-example-and-explanation %}