Merge pull request #35682 from github/repo-sync

Repo sync

.github/workflows/comment-release-note-info.yml

@@ -30,4 +30,4 @@ jobs:
             - If the change is urgent, post in `#docs-content-enterprise` on Slack.
             - Review the [style guide for release notes](https://docs.github.com/en/contributing/style-guide-and-content-model/style-guide#release-notes).
             - If you're updating or adding a note, add a datestamp in the format `[Updated: YYYY-MM-DD]`.
-            - If you're removing a note, add an "[Errata](https://docs.github.com/en/contributing/style-guide-and-content-model/style-guide#errata)" section with details of the change.
+            - If you're removing a note, add an [Errata](https://docs.github.com/en/contributing/style-guide-and-content-model/style-guide#errata) section with details of the change.

Dockerfile

@@ -140,20 +140,14 @@ COPY --chown=node:node --from=builder $APP_HOME/next.config.js ./
 COPY --chown=node:node --from=builder $APP_HOME/tsconfig.json ./
 
 # - - -
-# Environment variables
+# Environment variables are set in the Moda 
+# configuration: config/moda/configuration/*/env.yaml
 # - - -
+
 # This makes it possible to set `--build-arg BUILD_SHA=abc123`
 # and it then becomes available as an environment variable in the docker run.
 ARG BUILD_SHA
 ENV BUILD_SHA=$BUILD_SHA
-# We should always be running in production mode
-ENV NODE_ENV=production
-# Preferred port for server.js
-ENV PORT=4000
-# Include all languages
-ENV ENABLED_LANGUAGES="en,zh,es,pt,ru,ja,fr,de,ko"
-
-EXPOSE $PORT
 
 # Entrypoint to start the server
 # Note: Currently we have to use tsx because we have a mix of `.ts` and `.js` files with multiple import patterns

config/kubernetes/production/deployments/webapp.yaml

@@ -37,6 +37,10 @@ spec:
                 name: vault-secrets
             - configMapRef:
                 name: kube-cluster-metadata
+            # application-config is crated at deploy time from
+            # configuration set in config/moda/configuration/*/env.yaml
+            - configMapRef:
+                name: application-config
           # Zero-downtime deploys
           # https://thehub.github.com/engineering/products-and-services/internal/moda/feature-documentation/pod-lifecycle/#required-prestop-hook
           # https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/#container-hooks

config/moda/configuration/production/env.yaml

@@ -0,0 +1,8 @@
+data:
+  NODE_ENV: production
+  NODE_OPTIONS: '--max-old-space-size=4096'
+  PORT: '4000'
+  ENABLED_LANGUAGES: 'en,zh,es,pt,ru,ja,fr,de,ko'
+  HEROKU_APP_NAME: help-docs
+  HEROKU_PRODUCTION_APP: 'true'
+  RATE_LIMIT_MAX: '21'

content/admin/managing-iam/configuring-authentication-for-enterprise-managed-users/finding-the-object-id-for-your-entra-oidc-application.md

@@ -1,6 +1,6 @@
 ---
 title: Finding the object ID for your Entra OIDC application
-shortTitle: Find ID for Entra OIDC
+shortTitle: Find ID for Entra OIDC app
 intro: 'Learn how to find the object ID associated with your {% data variables.product.prodname_emus %} OIDC app.'
 product: '{% data reusables.gated-features.emus %}'
 versions:

content/code-security/code-scanning/managing-code-scanning-alerts/responsible-use-autofix-code-scanning.md

@@ -54,7 +54,7 @@ When {% data variables.product.prodname_copilot_autofix_short %} is enabled for
 
 Any {% data variables.product.prodname_copilot_autofix_short %} suggestions are generated and stored within the {% data variables.product.prodname_code_scanning %} backend. They are displayed as suggestions. No user interaction is needed beyond enabling {% data variables.product.prodname_code_scanning %} on the codebase and creating a pull request.
 
-The process of generating fixes does not gather or utilize any customer data beyond the scope outlined above. Therefore, the use of this feature is governed by the existing terms and conditions associated with {% data variables.product.prodname_GH_advanced_security %}. Moreover, data handled by {% data variables.product.prodname_copilot_autofix_short %} is strictly not employed for LLM training purposes. For more information on  {% data variables.product.prodname_GH_advanced_security %} terms and conditions, see [AUTOTITLE](/free-pro-team@latest/site-policy/github-terms/github-terms-for-additional-products-and-features#advanced-security){% ifversion fpt %}.{% else %} in the Free, Pro, & Team documentation.{% endif %}
+The process of generating fixes does not gather or utilize any customer data beyond the scope outlined above. Therefore, the use of this feature is governed by the existing terms and conditions associated with {% data variables.product.prodname_GH_advanced_security %}. Moreover, data handled by {% data variables.product.prodname_copilot_autofix_short %} is strictly not employed for LLM training purposes. For more information on {% data variables.product.prodname_GH_advanced_security %} terms and conditions, see "[AUTOTITLE](/free-pro-team@latest/site-policy/github-terms/github-terms-for-additional-products-and-features#advanced-security){% ifversion fpt %}."{% else %} in the Free, Pro, & Team documentation.{% endif %}
 
 ## Quality of suggestions
 

content/copilot/responsible-use-of-github-copilot-features/responsible-use-of-github-copilot-chat-in-github.md

@@ -89,7 +89,7 @@ However, it's important to note that {% data variables.product.prodname_copilot_
 
 ## Improving performance for {% data variables.product.prodname_copilot_chat_short %}
 
-{% data variables.product.prodname_copilot_chat_short %} can support a wide range of practical applications like Q&A, code generation, code analysis, and code fixes, each with different performance metrics and mitigation strategies. To enhance performance and address some of the  the limitations of {% data variables.product.prodname_copilot_chat_short %}, there are various measures that you can adopt. For more information on the limitations of {% data variables.product.prodname_copilot_chat_short %}, see [Limitations of {% data variables.product.prodname_copilot_chat %}](#limitations-of-github-copilot-chat).
+{% data variables.product.prodname_copilot_chat_short %} can support a wide range of practical applications like Q&A, code generation, code analysis, and code fixes, each with different performance metrics and mitigation strategies. To enhance performance and address some of the limitations of {% data variables.product.prodname_copilot_chat_short %}, there are various measures that you can adopt. For more information on the limitations of {% data variables.product.prodname_copilot_chat_short %}, see "[Limitations of {% data variables.product.prodname_copilot_chat %}](#limitations-of-github-copilot-chat)."
 
 ### Keep your prompts on topic
 

content/support/learning-about-github-support/about-copilot-in-github-support.md

@@ -53,7 +53,7 @@ Currently, {% data variables.product.prodname_copilot_in_support %} cannot take
 
 ## Best practices and use cases
 
-{% data variables.product.prodname_copilot_in_support %} is intended to answer your query related to {% data variables.product.prodname_dotcom %} products from {% data variables.product.prodname_dotcom %} documentation. More information provided in your input increases {% data variables.product.prodname_copilot_in_support %}'s likelihood of providing a relevant and helpful response that may also include best practices, tips, and solutions.  {% data variables.product.prodname_copilot_in_support %} consolidates information from multiple {% data variables.product.prodname_dotcom %} documents into a  tailored response, and may reduce the time required to answer your question. If you have a follow-up question or another {% data variables.product.prodname_dotcom %}-related query, you can continue using {% data variables.product.prodname_copilot_in_support %}.
+{% data variables.product.prodname_copilot_in_support %} is intended to answer your query related to {% data variables.product.prodname_dotcom %} products from {% data variables.product.prodname_dotcom %} documentation. More information provided in your input increases {% data variables.product.prodname_copilot_in_support %}'s likelihood of providing a relevant and helpful response that may also include best practices, tips, and solutions. {% data variables.product.prodname_copilot_in_support %} consolidates information from multiple {% data variables.product.prodname_dotcom %} documents into a tailored response, and may reduce the time required to answer your question. If you have a follow-up question or another {% data variables.product.prodname_dotcom %}-related query, you can continue using {% data variables.product.prodname_copilot_in_support %}.
 
 {% data variables.product.prodname_copilot_in_support %} also includes links to any documentation it uses when crafting an answer so that you're able to review the material or bookmark it for future reference. As with every large language model, it can make mistakes so please review the information provided to ensure it is free of errors.
 

data/glossaries/external.yml

@@ -79,7 +79,7 @@
   description: A movable square within a project board associated with an issue or pull request.
 - term: check
   description: >-
-    A check is a type of status check on {% data variables.product.product_name %}. See "[Status checks](#status-checks)."
+    A check is a type of status check on {% data variables.product.product_name %}. See [Status checks](#status-checks).
 - term: checkout
   description: >-
     You can use `git checkout` on the command line to create a new branch, change your current working branch to a different branch, or even to switch to a different version of a file from a different branch with `git checkout [branchname] [path to file]`. The "checkout" action updates all or part of the working tree with a tree object or
@@ -95,7 +95,7 @@
 - term: clean
   description: >-
     A working tree is clean if it corresponds to the revision referenced by the
-    current HEAD. Also see "[dirty](#dirty)."
+    current HEAD. Also see [dirty](#dirty).
 - term: clone
   description: >-
     A clone is a copy of a repository that lives on your computer instead of on
@@ -156,8 +156,8 @@
 - term: contributions
   description: >-
     Specific activities on GitHub that will:
-      - Add a square to a user's contribution graph: "[AUTOTITLE](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile#what-counts-as-a-contribution)"
-      - Add activities to a user's timeline on their profile: "[AUTOTITLE](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile#contribution-activity)"
+      - Add a square to a user's contribution graph: [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile#what-counts-as-a-contribution)
+      - Add activities to a user's timeline on their profile: [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile#contribution-activity)
 - term: contributor
   description: >-
     A contributor is someone who does not have collaborator access to a repository but has contributed to a project and had a pull request they opened merged into the repository.
@@ -173,7 +173,7 @@
   description: Used in command lines or scripts to transfer data.
 - term: dashboard
   description: >-
-    Your personal dashboard is the main hub of your activity on GitHub. From your personal dashboard, you can keep track of issues and pull requests you're following or working on, navigate to your top repositories and team pages, and learn about recent activity in repositories you're watching or participating in. You can also discover new repositories, which are recommended based on users you're following and repositories you have starred. To only view activity for a specific organization, visit your organization's dashboard. For more information, see "[AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard)" or "[AUTOTITLE](/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard)."
+    Your personal dashboard is the main hub of your activity on GitHub. From your personal dashboard, you can keep track of issues and pull requests you're following or working on, navigate to your top repositories and team pages, and learn about recent activity in repositories you're watching or participating in. You can also discover new repositories, which are recommended based on users you're following and repositories you have starred. To only view activity for a specific organization, visit your organization's dashboard. For more information, see [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard) or [AUTOTITLE](/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard).
 - term: default branch
   description: >-
     The base branch for new pull requests and code commits in a repository. Each repository has at least one branch, which Git creates when you initialize the repository. The first branch is usually called `main`, and is often the default branch.
@@ -337,7 +337,7 @@
     that they configure and control.
 - term: integration
   description: >-
-    A third-party application that integrates with GitHub. These are often {% data variables.product.prodname_github_apps %}, {% data variables.product.prodname_actions %}, or custom actions. For more information, see "[AUTOTITLE](/get-started/exploring-integrations/about-building-integrations)."
+    A third-party application that integrates with GitHub. These are often {% data variables.product.prodname_github_apps %}, {% data variables.product.prodname_actions %}, or custom actions. For more information, see [AUTOTITLE](/get-started/exploring-integrations/about-building-integrations).
 - term: issue
   description: >-
     Issues are suggested improvements, tasks or questions related to the
@@ -553,7 +553,7 @@
     Pull refers to when you are fetching in changes and merging them. For
     instance, if someone has edited the remote file you're both working on,
     you'll want to pull in those changes to your local copy so that it's up to
-    date. See also "[fetch](#fetch)."
+    date. See also [fetch](#fetch).
 - term: pull access
   description: A synonym for read access.
 - term: pull request
@@ -673,7 +673,7 @@
     days.
 - term: server-to-server request
   description: >-
-    An API request used by an application that acts as a bot, independently of any particular user. For example, an application that runs on a scheduled basis and closes issues where there has been no activity for a long time. Applications that use this type of authentication don't use a licensed GitHub account so, in an enterprise with a billing plan that allows a certain number of licenses to be used, a server-to-server bot is not consuming one of your GitHub licenses. The token used in a server-to-server request is acquired programmatically, via the GitHub API. For more information, see "[AUTOTITLE](/apps/creating-github-apps/authenticating-with-a-github-app/authenticating-as-a-github-app-installation)." See also, "[user-to-server request](#user-to-server-request)."
+    An API request used by an application that acts as a bot, independently of any particular user. For example, an application that runs on a scheduled basis and closes issues where there has been no activity for a long time. Applications that use this type of authentication don't use a licensed GitHub account so, in an enterprise with a billing plan that allows a certain number of licenses to be used, a server-to-server bot is not consuming one of your GitHub licenses. The token used in a server-to-server request is acquired programmatically, via the GitHub API. For more information, see [AUTOTITLE](/apps/creating-github-apps/authenticating-with-a-github-app/authenticating-as-a-github-app-installation). See also, [user-to-server request](#user-to-server-request).
 - term: service hook
   description: >-
     Also called "webhook." Webhooks provide a way for notifications to be
@@ -700,7 +700,7 @@
     conditions set for the repository you're contributing to.
 - term: status checks
   description: >-
-    Status checks are external processes, such as continuous integration builds, which run for each commit you make in a repository. For more information, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)."
+    Status checks are external processes, such as continuous integration builds, which run for each commit you make in a repository. For more information, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks).
 - term: star
   description: >-
     A bookmark or display of appreciation for a repository. Stars are a manual
@@ -762,7 +762,7 @@
   description: A user's handle on GitHub.
 - term: user-to-server request
   description: >-
-    An API request used by an application that performs a task on behalf of a particular user. Where a task is carried out with user-to-server authentication it's shown on GitHub as having been done by a user via an application. For example, you might choose to create an issue from within a third-party application, and the application would do this on your behalf on GitHub. The scope of tasks an application can perform using a user-to-server request is restricted by both the app's and the user's permissions and access. The token used in a user-to-server request is acquired via OAuth. For more information, see "[AUTOTITLE](/apps/creating-github-apps/authenticating-with-a-github-app/authenticating-with-a-github-app-on-behalf-of-a-user)." See also, "[server-to-server request](#server-to-server-request)."
+    An API request used by an application that performs a task on behalf of a particular user. Where a task is carried out with user-to-server authentication it's shown on GitHub as having been done by a user via an application. For example, you might choose to create an issue from within a third-party application, and the application would do this on your behalf on GitHub. The scope of tasks an application can perform using a user-to-server request is restricted by both the app's and the user's permissions and access. The token used in a user-to-server request is acquired via OAuth. For more information, see [AUTOTITLE](/apps/creating-github-apps/authenticating-with-a-github-app/authenticating-with-a-github-app-on-behalf-of-a-user). See also, [server-to-server request](#server-to-server-request).
 - term: visible team
   description: A team that can be viewed and @mentioned by every organization member.
 - term: watch

data/release-notes/PLACEHOLDER-TEMPLATE.yml

@@ -8,7 +8,7 @@ intro: |
   >
   > If {% data variables.location.product_location %} is running an RC, you cannot upgrade to the general availability (GA) release. You also cannot upgrade with a hotpatch.
 
-  For upgrade instructions, see "[AUTOTITLE](/admin/upgrading-your-instance/preparing-to-upgrade/overview-of-the-upgrade-process)."
+  For upgrade instructions, see [AUTOTITLE](/admin/upgrading-your-instance/preparing-to-upgrade/overview-of-the-upgrade-process).
 sections:
   # Remove section heading if the section contains no notes.