Merge remote-tracking branch 'docs-internal/main'

heiskr · heiskr · commit 26dfbb854a5a · 2025-07-17T08:03:21.000-07:00
diff --git a/content/actions/concepts/runners/about-larger-runners.md b/content/actions/concepts/runners/about-larger-runners.md
@@ -30,6 +30,8 @@ The following machines sizes are available for macOS {% data variables.actions.h
 
 {% data reusables.actions.larger-runners-table %}
 
+>[!NOTE] The XLarge macOS runner is in public preview and subject to change.
+
 #### Limitations for macOS {% data variables.actions.hosted_runners %}
 
 {% data reusables.actions.macos-runner-limitations %}
@@ -82,7 +84,7 @@ You can choose from several specifications for {% data variables.actions.hosted_
 
 | CPU | Memory (RAM)  | Storage (SSD) | Architecture | Operating system (OS) |
 | --- | ------------- | ------------- | ------------ | --------------------- |
-| 6   | 14 GB         | 14 GB         | arm64        | macOS                 |
+| 5   | 14 GB         | 14 GB         | arm64        | macOS                 |
 | 12  | 30 GB         | 14 GB         | x64          | macOS                 |
 | 2   | 8 GB          | 75 GB         | x64, arm64   | Ubuntu                |
 | 4   | 16 GB         | 150 GB        | x64, arm64   | Ubuntu, Windows       |
@@ -95,6 +97,8 @@ You can choose from several specifications for {% data variables.actions.hosted_
 
 >[!NOTE] The 4-vCPU Windows runner only works with the Windows Server 2025 or the Base Windows 11 Desktop image.
 
+>[!NOTE] The 5-vCPU macOS runner is in public preview and subject to change.
+
 ### Specifications for GPU {% data variables.actions.hosted_runners %}
 
 | CPU | GPU | GPU card | Memory (RAM) | GPU memory (VRAM) | Storage (SSD) | Operating system (OS) |
diff --git a/content/code-security/dependabot/working-with-dependabot/configuring-access-to-private-registries-for-dependabot.md b/content/code-security/dependabot/working-with-dependabot/configuring-access-to-private-registries-for-dependabot.md
@@ -160,7 +160,8 @@ Examples of how to configure access to the private registries supported by {% da
 * [`cargo-registry`](#cargo-registry)
 * [`composer-repository`](#composer-repository)
 * [`docker-registry`](#docker-registry)
-* [`git`](#git)
+* [`git`](#git){% ifversion dependabot-helm-support %}
+* [`helm-registry`](#helm-registry){% endif %}
 * [`hex-organization`](#hex-organization)
 * [`hex-repository`](#hex-repository)
 * [`maven-repository`](#maven-repository)
diff --git a/content/copilot/concepts/about-organizing-and-sharing-context-with-copilot-spaces.md b/content/copilot/concepts/about-organizing-and-sharing-context-with-copilot-spaces.md
@@ -14,7 +14,7 @@ redirect_from:
 
 {% data reusables.copilot.copilot-spaces.preview-note %}
 
-{% data variables.copilot.copilot_spaces %} let you organize the context that {% data variables.product.prodname_copilot_short %} uses to answer your questions. {% data variables.copilot.copilot_spaces_short %} can include code from repositories, free-text content like transcripts or notes, and more—grouped together in one place. You can ask {% data variables.product.prodname_copilot_short %} questions grounded in that context, or share the space with your team to support collaboration and knowledge sharing.
+{% data variables.copilot.copilot_spaces %} let you organize the context that {% data variables.product.prodname_copilot_short %} uses to answer your questions. {% data variables.copilot.copilot_spaces_short %} can include code, pull requests, or issues from repositories, free-text content like transcripts or notes, images, and file uploads. You can ask {% data variables.product.prodname_copilot_short %} questions grounded in that context, or share the space with your team to support collaboration and knowledge sharing.
 
 ## Why use {% data variables.copilot.copilot_spaces %}?
 
@@ -37,7 +37,7 @@ With {% data variables.copilot.copilot_spaces %} you can:
 | -------------------- | --------------------------- | -------------------------------------------------------------- |
 | Who can create   | Anyone with a {% data variables.product.prodname_copilot_short %} license             | Organization owners                                              |
 | Owned by   | Organizations or individual users              | Organizations                             |
-| Content type     | Any code, pull requests, or issues hosted in repositories and free-text content                  | Markdown files hosted in {% data variables.product.github %}
+| Content type     | Files and directories from {% data variables.product.github %} repositories, pull requests and issues, uploaded files including images, text files, rich documents, and spreadsheets, and free-text content                   | Markdown files hosted in {% data variables.product.github %} |
 | Context handling | Limited in size, which guarantees higher response quality given the focused selection | Unlimited, but that comes with reduced response quality |
 
 {% endrowheaders %}
diff --git a/content/copilot/how-tos/context/copilot-spaces/collaborating-with-your-team-using-copilot-spaces.md b/content/copilot/how-tos/context/copilot-spaces/collaborating-with-your-team-using-copilot-spaces.md
@@ -23,7 +23,7 @@ redirect_from:
 
 ## Use cases for team collaboration
 
-* **Onboarding**: Share a space with key code, docs, and checklists to help new developers get started faster.
+* **Onboarding**: Share a space with code, documentation, diagrams, and checklists to help new developers get started faster.
 * **System knowledge**: Create a space for a complex system or workflow (like authentication or CI pipelines) that other people can reference.
 * **Style guides or review checklists**: Document standards and examples in a space that {% data variables.product.prodname_copilot_short %} can reference when suggesting changes.
 
diff --git a/content/copilot/how-tos/context/copilot-spaces/creating-and-using-copilot-spaces.md b/content/copilot/how-tos/context/copilot-spaces/creating-and-using-copilot-spaces.md
@@ -12,8 +12,12 @@ redirect_from:
   - /copilot/using-github-copilot/copilot-spaces/creating-and-using-copilot-spaces
 ---
 
+For an overview of {% data variables.copilot.copilot_spaces %}, see [AUTOTITLE](/copilot/concepts/about-organizing-and-sharing-context-with-copilot-spaces).
+
 {% data reusables.copilot.copilot-spaces.preview-note %}
 
+## Creating a space
+
 1. To create a space, go to [https://github.com/copilot/spaces](https://github.com/copilot/spaces), and click **Create space**.
 1. Give your space a name.
 1. Choose whether the space is owned by you or by an organization you belong to. Organization-owned {% data variables.copilot.copilot_spaces_short %} can be shared using {% data variables.product.github %}’s built-in permission model.
@@ -23,7 +27,7 @@ redirect_from:
 
 1. Click **Save** in the top right corner of the page.
 
-## Adding context to {% data variables.copilot.copilot_spaces_short %}
+## Adding context to a space
 
 You can add two types of context to your space:
 
@@ -37,11 +41,12 @@ You can add two types of context to your space:
 
   To add attachments, click **{% octicon "plus" aria-hidden="true" aria-label="plus" %} Add** to the right of "Attachments", then choose one of the following options:
 
-  * **{% octicon "file-code" aria-hidden="true" aria-label="file-code" %} Add files, folders...**: You can add files and folders from your {% data variables.product.github %} repositories. This includes code files, documentation, and other relevant content that can help {% data variables.product.prodname_copilot_short %} understand the context of your space.
-  * **{% octicon "plus" aria-hidden="true" aria-label="plus" %} Add a text file...**: You can add free-text content, such as transcripts, notes, or any other relevant information that can help {% data variables.product.prodname_copilot_short %} understand the context of your space.
-  * **{% octicon "paste" aria-hidden="true" aria-label="paste" %} Add via {% data variables.product.github %} URL...**: You can paste the URLs of the {% data variables.product.github %} content you want to add. This can include issues and pull requests.
+  * **{% octicon "file-code" aria-hidden="true" aria-label="file-code" %} Attach files and folders**: You can add files and folders from your {% data variables.product.github %} repositories. This includes code files, documentation, and other relevant content that can help {% data variables.product.prodname_copilot_short %} understand the context of your space.
+  * **{% octicon "link" aria-hidden="true" aria-label="link" %} Link pull requests and issues**: You can paste the URLs of the {% data variables.product.github %} issues and pull requests.
+  * **{% octicon "upload" aria-hidden="true" aria-label="upload" %} Upload a file**: You can upload files directly from your local machine. This includes images, text files, rich documents, and spreadsheets.
+  * **{% octicon "paste" aria-hidden="true" aria-label="paste" %} Add text content**: You can type or paste free-text content, such as transcripts, notes, or any other relevant information that can help {% data variables.product.prodname_copilot_short %} understand the context of your space.
 
-## Using {% data variables.copilot.copilot_spaces_short %}
+## Using {% data variables.copilot.copilot_spaces %}
 
 Once you've added context to your space, you can ask {% data variables.product.prodname_copilot_short %} questions in the chat interface. Your chat will be grounded in the context you've added.
 
diff --git a/content/copilot/how-tos/set-up/setting-up-github-copilot-for-your-enterprise.md b/content/copilot/how-tos/set-up/setting-up-github-copilot-for-your-enterprise.md
@@ -41,6 +41,6 @@ Enable {% data variables.product.prodname_copilot_short %} for some or all organ
 
 If your enterprise is on {% data variables.enterprise.data_residency_site %}, users must perform some additional setup to authenticate to their account from their development environment. See [AUTOTITLE](/copilot/managing-copilot/configure-personal-settings/using-github-copilot-with-an-account-on-ghecom).
 
-## 5. Drive {% data variables.product.prodname_copilot_short %} adoption
+## Next steps
 
-Planning and implementing an effective enablement process is essential to drive adoption of {% data variables.product.prodname_copilot_short %} in your enterprise. See [AUTOTITLE](/copilot/rolling-out-github-copilot-at-scale/driving-copilot-adoption-in-your-company).
+{% data reusables.copilot.setup-next-steps %}
diff --git a/content/copilot/how-tos/set-up/setting-up-github-copilot-for-your-organization.md b/content/copilot/how-tos/set-up/setting-up-github-copilot-for-your-organization.md
@@ -35,22 +35,10 @@ You may also need to install custom SSL certificates on your members' machines.
 
 ## 4. Grant access to members
 
-Enable {% data variables.product.prodname_copilot_short %} for some or all members of your organization. See [AUTOTITLE](/copilot/managing-copilot/managing-github-copilot-in-your-organization/managing-access-to-github-copilot-in-your-organization/granting-access-to-copilot-for-members-of-your-organization).
-
-To help drive adoption of {% data variables.product.prodname_copilot_short %} in your organization, think about what teams or members are most excited about {% data variables.product.prodname_copilot_short %} or could benefit the most from {% data variables.product.prodname_copilot_short %}. You may want to enable {% data variables.product.prodname_copilot_short %} for those members before enabling {% data variables.product.prodname_copilot_short %} for your whole organization. This can help you discover blockers, demonstrate early success, and set your organization up for a successful {% data variables.product.prodname_copilot_short %} rollout.
-
-{% data reusables.copilot.self-serve-license-link %}
+Enable {% data variables.product.prodname_copilot_short %} for some or all members of your organization. You may want to identify teams or members who are most likely to benefit from {% data variables.product.prodname_copilot_short %} and enable {% data variables.product.prodname_copilot_short %} for them first to discover potential blockers and demonstrate early success. See [AUTOTITLE](/copilot/managing-copilot/managing-github-copilot-in-your-organization/managing-access-to-github-copilot-in-your-organization/granting-access-to-copilot-for-members-of-your-organization).
 
 If your organization is part of an enterprise on {% data variables.enterprise.data_residency_site %}, users must perform some additional setup to authenticate to their account from their development environment. See [AUTOTITLE](/copilot/managing-copilot/configure-personal-settings/using-github-copilot-with-an-account-on-ghecom).
 
-## 5. Drive {% data variables.product.prodname_copilot_short %} adoption
-
-Planning and implementing an effective enablement process is essential to drive adoption of {% data variables.product.prodname_copilot_short %} in your organization. See [AUTOTITLE](/copilot/rolling-out-github-copilot-at-scale/driving-copilot-adoption-in-your-company).
-
-## 6. Enhance the {% data variables.product.prodname_copilot_short %} experience
-
-Enhance the {% data variables.product.prodname_copilot_short %} experience for your organization by:
+## Next steps
 
-* **Setting up knowledge bases** for use with {% data variables.copilot.copilot_chat_short %} _({% data variables.copilot.copilot_enterprise_short %} only)_. See [AUTOTITLE](/enterprise-cloud@latest/copilot/managing-copilot/managing-github-copilot-in-your-organization/managing-github-copilot-features-in-your-organization/managing-copilot-knowledge-bases).
-* **Installing {% data variables.copilot.copilot_extensions_short %}** to integrate other tools with {% data variables.copilot.copilot_chat_short %}. See [AUTOTITLE](/copilot/managing-copilot/managing-github-copilot-in-your-organization/managing-github-copilot-features-in-your-organization/installing-github-copilot-extensions-for-your-organization).
-* **Adding {% data variables.copilot.copilot_coding_agent %}** as a team member to work asynchronously on issues. See [AUTOTITLE](/copilot/rolling-out-github-copilot-at-scale/enabling-developers/using-copilot-coding-agent-in-org).
+{% data reusables.copilot.setup-next-steps %}
diff --git a/content/copilot/tutorials/speeding-up-development-work-with-copilot-spaces.md b/content/copilot/tutorials/speeding-up-development-work-with-copilot-spaces.md
@@ -26,7 +26,7 @@ Below are some examples of how to use {% data variables.copilot.copilot_spaces_s
 
 ## Developing a new feature
 
-When working on a specific feature, you can save time and produce higher-quality results by using a space. Add the relevant code, a product spec, and any supporting materials—like notes from a design review or image descriptions of mockups. {% data variables.product.prodname_copilot_short %} can help you:
+When working on a specific feature, you can save time and produce higher-quality results by using a space. Add the relevant code, a product spec, and any supporting materials—like notes from a design review or mockup images. {% data variables.product.prodname_copilot_short %} can help you:
 
 * Summarize how the current implementation works.
 * Suggest changes or additions based on the spec.
@@ -41,7 +41,7 @@ When working on a specific feature, you can save time and produce higher-quality
 
 ## Defining the logic for a small, frequent task
 
-When working on repetitive tasks like tracking telemetry events or handling event emissions, it’s useful to document the logic once and share it with others through {% data variables.copilot.copilot_spaces_short %}. This allows everyone to stay consistent and saves time when performing the task. {% data variables.product.prodname_copilot_short %} can assist by:
+When working on repetitive tasks like tracking telemetry events or handling event emissions, it’s useful to document the logic once and share it with others through {% data variables.copilot.copilot_spaces_short %}. This allows everyone to stay consistent and saves time when performing the task. If you have a process flowchart for a task, you can upload this to your space for reference. {% data variables.product.prodname_copilot_short %} can assist by:
 
 * Suggesting efficient patterns based on your previous work.
 * Helping write reusable functions or templates.
diff --git a/data/reusables/actions/larger-runners-table.md b/data/reusables/actions/larger-runners-table.md
@@ -1,4 +1,4 @@
 | Runner Size | Architecture| Processor (CPU)| Memory (RAM)  | Storage (SSD) | Workflow label                                                                                                                                   |
 | ------------| ------------| -------------- | ------------- | ------------- |--------------------------------------------------------------------------------------------------------------------------------------------------|
 | Large       | Intel       | 12             | 30 GB         | 14 GB         | <code>macos-latest-large</code>, <code>macos-13-large</code>, <code>macos-14-large</code> [latest], <code>macos-15-large</code> |
-| XLarge      | arm64 (M1)  | 6 (+ 8 GPU hardware acceleration) | 14 GB         | 14 GB         | <code>macos-latest-xlarge</code>, <code>macos-13-xlarge</code> , <code>macos-14-xlarge</code> [latest], <code>macos-15-xlarge</code> |
+| XLarge      | arm64 (M2)  | 5 (+ 8 GPU hardware acceleration) | 14 GB         | 14 GB         | <code>macos-latest-xlarge</code>, <code>macos-13-xlarge</code>, <code>macos-14-xlarge</code> [latest], <code>macos-15-xlarge</code> |
diff --git a/data/reusables/contributing/content-linter-rules.md b/data/reusables/contributing/content-linter-rules.md
@@ -72,4 +72,5 @@
 | GHD046 | outdated-release-phase-terminology | Outdated release phase terminology should be replaced with current GitHub terminology | warning | terminology, consistency, release-phases |
 | GHD048 | british-english-quotes | Periods and commas should be placed inside quotation marks (American English style) | warning | punctuation, quotes, style, consistency |
 | GHD050 | multiple-emphasis-patterns | Do not use more than one emphasis/strong, italics, or uppercase for a string | warning | formatting, emphasis, style |
-| GHD049 | note-warning-formatting | Note and warning tags should be formatted according to style guide | warning | formatting, callouts, notes, warnings, style |
+| GHD049 | note-warning-formatting | Note and warning tags should be formatted according to style guide | warning | formatting, callouts, notes, warnings, style |
+| GHD051 | frontmatter-versions-whitespace | Versions frontmatter should not contain unnecessary whitespace | warning | frontmatter, versions |
diff --git a/data/reusables/copilot/setup-next-steps.md b/data/reusables/copilot/setup-next-steps.md
@@ -0,0 +1,4 @@
+* **Explore self-service license management options**. Many successful rollouts use a self-service model where developers can claim a license without approval. See [AUTOTITLE](/copilot/rolling-out-github-copilot-at-scale/setting-up-a-self-serve-process-for-github-copilot-licenses).
+* **Learn how to plan and implement an effective enablement process to drive {% data variables.product.prodname_copilot_short %} adoption**. See [AUTOTITLE](/copilot/rolling-out-github-copilot-at-scale/driving-copilot-adoption-in-your-company).
+* **Enhance the development experience by enabling and training developers on the latest features**. For example, share context with {% data variables.copilot.copilot_spaces %}, enable {% data variables.copilot.copilot_code-review_short %} on pull requests, and allow developers to experiment with prompts using {% data variables.product.prodname_github_models %}. For an example showing how these features fit together, see [AUTOTITLE](/copilot/tutorials/rolling-out-github-copilot-at-scale/enabling-developers/integrating-agentic-ai).
+* **Add {% data variables.copilot.copilot_coding_agent %} as a team member for asynchronous issue work**. See [AUTOTITLE](/copilot/rolling-out-github-copilot-at-scale/enabling-developers/using-copilot-coding-agent-in-org).
diff --git a/src/content-linter/lib/linting-rules/frontmatter-versions-whitespace.js b/src/content-linter/lib/linting-rules/frontmatter-versions-whitespace.js
diff --git a/src/content-linter/lib/linting-rules/index.js b/src/content-linter/lib/linting-rules/index.js
diff --git a/src/content-linter/style/github-docs.js b/src/content-linter/style/github-docs.js
diff --git a/src/content-linter/tests/unit/frontmatter-versions-whitespace.js b/src/content-linter/tests/unit/frontmatter-versions-whitespace.js
