Merge branch 'main' into patch-1

Author: Sharra-writes

content/billing/concepts/budgets-and-alerts.md

@@ -30,6 +30,10 @@ Each budget has a type and a scope that define which paid use contributes to spe
 * **Type**: Defines which metered product or SKU is measured.
 * **Scope**: Defines whether the budget applies to the whole account, or to a subset of repositories, organizations, or cost centers (enterprise only).
 
+## Budget alerts
+
+You can enable alerts for budgets to receive emails when usage reaches 75%, 90%, and 100% of the budget amount. Emails are sent to account owners and billing managers by default. Additional recipients can be added as needed.
+
 ## Your first billing cycle after creating a budget
 
 When you first create a budget, be aware that the budget applies only to metered usage from the date of its creation onwards. Any use made before you created the budget is not included in the calculations. This means that you may exceed your budget in the first billing cycle after you create your budget, even if you select the option stop usage when the limit is reached.

content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md

@@ -22,15 +22,15 @@ shortTitle: Configure
 {% data reusables.repositories.sidebar-settings %}
 1. In the "Features" section, under **Issues**, click **Set up templates**. You may need to enable **Issues** and refresh the page before you can see the button.
 
-![Screenshot of the "Features" section of a repository's settings, with the "Issues" setting ticked and the green "Set up templates" button visible.](/assets/images/help/repository/set-up-issue-templates-button.png)
+   ![Screenshot of the "Features" section of a repository's settings, with the "Issues" setting ticked and the green "Set up templates" button visible.](/assets/images/help/repository/set-up-issue-templates-button.png)
 1. Use the **Add template** dropdown menu, and click on the type of template you'd like to create.
 
    ![Screenshot of the "Add template" dropdown menu expanded to show standard templates, "Bug report" and "Feature request," with a "Custom template".](/assets/images/help/repository/add-template-drop-down-menu.png)
 1. To preview or edit the template before committing it to the repository, next to the template, click **Preview and edit**.
 1. To edit the template, click {% octicon "pencil" aria-label="Edit template" %}, and type in the fields to edit their contents.
 
    ![Screenshot of the preview of an issue template. To the right of the template name, a pencil icon is outlined in dark orange.](/assets/images/help/repository/issue-template-edit-button.png)
-1. To automatically set a default issue title, assign the issue to people with read access to the repository, or apply labels to issues raised from the template, use the fields under "Optional additional information." You can also add these details in the issue template with `title`, `labels`, or `assignees` in a YAML frontmatter format.
+1. To automatically set a default issue title, assign the issue to people with read access to the repository, or apply labels to issues raised from the template, use the fields under "Optional additional information." You can also add these details in the issue template with `title`, `labels`, `type`, or `assignees` in a YAML frontmatter format.
 1. When you're finished editing and previewing your template, click **Propose changes** in the upper right corner of the page.
 1. In the "Commit message" field, type a commit message describing your changes.
 1. Below the commit message fields, select whether to commit your template directly to the default branch, or to create a new branch and open a pull request. For more information about pull requests, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).

content/copilot/concepts/agents/coding-agent/mcp-and-coding-agent.md

@@ -20,9 +20,7 @@ The agent can use tools provided by local and remote MCP servers. Some MCP serve
 
 For more information on MCP, see [the official MCP documentation](https://modelcontextprotocol.io/introduction). For information on some of the currently available MCP servers, see [the MCP servers repository](https://github.com/modelcontextprotocol/servers/tree/main).
 
-> [!NOTE]
-> * {% data variables.copilot.copilot_coding_agent %} only supports tools provided by MCP servers. It does not support resources or prompts.
-> * {% data variables.copilot.copilot_coding_agent %} does not currently support remote MCP servers that leverage OAuth for authentication and authorization.
+{% data reusables.copilot.mcp.coding-agent-limitations %}
 
 ## Default MCP servers
 

content/copilot/how-tos/use-copilot-agents/coding-agent/extend-coding-agent-with-mcp.md

@@ -29,6 +29,8 @@ As a repository administrator, you can configure MCP servers for use within your
 > [!WARNING]
 > Once you've configured an MCP server, {% data variables.product.prodname_copilot_short %} will be able to use the tools provided by the server autonomously, and will not ask for your approval before using them.
 
+{% data reusables.copilot.mcp.coding-agent-limitations %}
+
 ## Adding an MCP configuration to your repository
 
 Repository administrators can configure MCP servers by following these steps:

content/enterprise-onboarding/index.md

@@ -40,6 +40,26 @@ journeyTracks:
       - '/enterprise-onboarding/support-for-your-enterprise/understanding-support'
       - '/enterprise-onboarding/support-for-your-enterprise/using-the-support-portal'
       - '/enterprise-onboarding/support-for-your-enterprise/managing-support-entitlements'
+  - id: 'github_actions'
+    title: 'Getting started with GitHub Actions'
+    description: 'Learn how to plan and implement a rollout of {% data variables.product.prodname_actions %} for your enterprise.'
+    guides:
+      - '/enterprise-onboarding/github-actions-for-your-enterprise/about-github-actions-for-enterprises'
+      - '/enterprise-onboarding/github-actions-for-your-enterprise/understanding-github-actions'
+      - '/enterprise-onboarding/github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise'
+      - '/enterprise-onboarding/github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions'
+      - '/enterprise-onboarding/github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud'
+      - '/enterprise-onboarding/github-actions-for-your-enterprise/security-hardening-for-github-actions'
+      - '/enterprise-onboarding/github-actions-for-your-enterprise/about-billing-for-github-actions'
+  - id: 'feature_enhancements'
+    title: 'Enhancing your experience'
+    description: 'Take advantage of features available with {% data variables.product.prodname_ghe_cloud %}.'
+    guides:
+      - '/enterprise-onboarding/feature-enhancements/about-the-audit-log-for-your-enterprise'
+      - '/enterprise-onboarding/feature-enhancements/about-access-permissions-on-github'
+      - '/enterprise-onboarding/feature-enhancements/about-rulesets'
+      - '/enterprise-onboarding/feature-enhancements/create-a-readme-for-your-enterprise'
+      - '/enterprise-onboarding/feature-enhancements/about-enterprise-security'
 versions:
   ghec: '*'
 topics:

content/repositories/creating-and-managing-repositories/about-repositories.md

@@ -109,14 +109,7 @@ People with admin permissions for a repository can change an existing repository
 
 {% endif %}
 
-All enterprise members have read permissions to the internal repository, but internal repositories are not visible to people {% ifversion fpt or ghec %}outside of the enterprise{% else %}who are not members of any organization{% endif %}, including outside collaborators on organization repositories. For more information, see [AUTOTITLE](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-members) and [AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization).
-
-{% ifversion ghes %}
-
-> [!NOTE]
-> A user must be part of an organization to be an enterprise member and have access to internal repositories. If a user on {% data variables.location.product_location %} is not a member of any organization, that user will not have access to internal repositories.
-
-{% endif %}
+Organization members have read permissions to all internal repositories in an enterprise, including those in organizations they are not a member of. Internal repositories are not visible to people {% ifversion fpt or ghec %}outside of the enterprise{% else %}who are not members of any organization{% endif %}, including outside collaborators on organization repositories. For more information, see [AUTOTITLE](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-members) and [AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization).
 
 {% data reusables.repositories.internal-repo-default %}
 

content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-default-branch-name-for-your-repositories.md

@@ -27,7 +27,7 @@ When you create a new repository on {% data variables.product.github %}, the rep
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.repo-tab %}
-1. In the text field, type the default name that you would like to use for new branches.
+1. In the text field, type the default name that you would like to use for new repositories.
 1. Click **Update**.
 
 ## Further reading

data/reusables/code-scanning/codeql-query-tables/links-to-all-tables.md

@@ -9,4 +9,5 @@
 * [AUTOTITLE](/code-security/code-scanning/managing-your-code-scanning-configuration/javascript-typescript-built-in-queries)
 * [AUTOTITLE](/code-security/code-scanning/managing-your-code-scanning-configuration/python-built-in-queries)
 * [AUTOTITLE](/code-security/code-scanning/managing-your-code-scanning-configuration/ruby-built-in-queries)
+* [AUTOTITLE](/code-security/code-scanning/managing-your-code-scanning-configuration/rust-built-in-queries)
 * [AUTOTITLE](/code-security/code-scanning/managing-your-code-scanning-configuration/swift-built-in-queries)

data/reusables/community/issue-forms-sample.md

@@ -5,7 +5,8 @@ title: "[Bug]: "
 labels: ["bug", "triage"]
 projects: ["octo-org/1", "octo-org/44"]
 assignees:
-  - octocat
+  - octocat{% ifversion issue-types %}
+type: bug{% endif %}
 body:
   - type: markdown
     attributes:
@@ -59,7 +60,7 @@ body:
     id: terms
     attributes:
       label: Code of Conduct
-      description: By submitting this issue, you agree to follow our [Code of Conduct](https://example.com). 
+      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

data/reusables/copilot/mcp/coding-agent-limitations.md

@@ -0,0 +1,3 @@
+> [!NOTE]
+> * {% data variables.copilot.copilot_coding_agent %} only supports tools provided by MCP servers. It does not support resources or prompts.
+> * {% data variables.copilot.copilot_coding_agent %} does not currently support remote MCP servers that leverage OAuth for authentication and authorization.