Repo sync

Dockerfile

@@ -8,7 +8,7 @@
 # ---------------------------------------------------------------
 # To update the sha:
 # https://github.com/github/gh-base-image/pkgs/container/gh-base-image%2Fgh-base-noble
-FROM ghcr.io/github/gh-base-image/gh-base-noble:20251217-105955-g05726ec4c AS base
+FROM ghcr.io/github/gh-base-image/gh-base-noble:20260109-173439-g06c82aab1 AS base
 
 # Install curl for Node install and determining the early access branch
 # Install git for cloning docs-early-access & translations repos

content/account-and-profile/concepts/account-management.md

@@ -13,19 +13,26 @@ redirect_from:
   - /account-and-profile/concepts/personal-account-management
 ---
 
+{% ifversion ghes < 3.21 %}
 ## About converting your personal account
 
 Converting a personal account into an organization allows you move to a shared account where a large number of people can collaborate across many projects at once. Converting your account:
 * Preserves the repositories as they are without the need to transfer them to another account manually
 * Automatically invites collaborators to teams with permissions equivalent to what they had before
-{%- ifversion fpt or ghec %}
-* For personal accounts on {% data variables.product.prodname_pro %}, automatically transitions billing to [the paid {% data variables.product.prodname_team %}](/billing/managing-the-plan-for-your-github-account/about-billing-for-plans) without the need to re-enter payment information, adjust your billing cycle, or double pay at any time
-{%- endif %}
 
 When you convert a personal account into an organization, we'll add collaborators on repositories that belong to the account to the new organization as outside collaborators. You can then invite outside collaborators to become members of your new organization if you wish. For more information, see [AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators).
 
 To convert your personal account into an organization, see [AUTOTITLE](/account-and-profile/how-tos/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/converting-a-user-into-an-organization).
 
+{% else %}
+
+## About moving your work to an organization
+
+You can move repositories and projects from your personal account to an organization while keeping your personal account intact. This enables team collaboration with granular permissions across your existing work.
+
+For more information, see [AUTOTITLE](/account-and-profile/how-tos/account-management/moving-your-work-to-an-organization).
+{% endif %}
+
 ## About deletion of your personal account
 
 Deleting your personal account removes all repositories, forks of private repositories, wikis, issues, pull requests, and pages owned by your account. {% ifversion fpt or ghec %}Issues and pull requests you've created and comments you've made in repositories owned by other users will not be deleted. Your resources and comments will become associated with the [ghost user](https://github.com/ghost).{% else %}Issues and pull requests you've created and comments you've made in repositories owned by other users will not be deleted.{% endif %}

content/account-and-profile/how-tos/account-management/converting-a-user-into-an-organization.md

@@ -12,9 +12,7 @@ redirect_from:
   - /account-and-profile/how-tos/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/converting-a-user-into-an-organization
 intro: You can convert your personal account into an organization. This allows more granular permissions for repositories that belong to the organization.
 versions:
-  fpt: '*'
-  ghes: '*'
-  ghec: '*'
+  ghes: '<3.21'
 topics:
   - Accounts
 shortTitle: Convert your account
@@ -25,9 +23,7 @@ contentType: how-tos
 
 The personal account you want to convert cannot be a member of any organizations. If the personal account you want to convert is a member of an organization, you must leave the organization before you can convert the account.
 
-{% ifversion ghes %}
-You may not be able to convert a personal account into an organization, if an enterprise owner has set a policy at the enterprise level. See, [AUTOTITLE](/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/preventing-users-from-creating-organizations).
-{% endif %}
+You may not be able to convert a personal account into an organization if an enterprise owner has set a policy at the enterprise level. See, [AUTOTITLE](/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/preventing-users-from-creating-organizations).
 
 ## Keep your personal account and create a new organization manually
 
@@ -56,7 +52,4 @@ To convert your personal account into an organization, follow these steps:
 
 * [AUTOTITLE](/account-and-profile/reference/personal-account-reference#side-effects-of-converting-an-account-to-an-organization)
 * [AUTOTITLE](/organizations/organizing-members-into-teams)
-{% ifversion fpt or ghec %}
-* [AUTOTITLE](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)
-{% endif %}
 * [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/accessing-an-organization)

content/account-and-profile/how-tos/account-management/index.md

@@ -1,6 +1,6 @@
 ---
 title: Managing your personal account
-intro: You can manage your personal account on {% data variables.product.github %}. For example, you can {% ifversion fpt or ghec %}manage multiple accounts, {% endif %}convert an account to an organization, or delete an account.
+intro: You can manage your personal account on {% data variables.product.github %}. For example, you can change your username, {% ifversion fpt or ghec %}manage multiple accounts, {% endif %}{% ifversion ghes < 3.21 %}convert an account to an organization, {% else %}move your work to an organization, {% endif %}or delete an account.
 shortTitle: Personal account management
 versions:
   fpt: '*'
@@ -12,6 +12,7 @@ children:
   - /managing-multiple-accounts
   - /merging-multiple-personal-accounts
   - /changing-your-username
+  - /moving-your-work-to-an-organization
   - /converting-a-user-into-an-organization
   - /unlinking-your-email-address-from-a-locked-account
   - /deleting-your-personal-account

content/account-and-profile/how-tos/account-management/moving-your-work-to-an-organization.md

@@ -0,0 +1,32 @@
+---
+title: Moving your work to an organization
+intro: You can transfer repositories and projects from your personal account to a new or existing organization through your account settings.
+versions:
+  fpt: '*'
+  ghes: '>= 3.21'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Move work to organization
+---
+
+## Keeping your username for the organization
+
+If you want your new organization to use your current personal account username, you'll need to rename your personal account first:
+
+1. Change your personal account username to something new. For more information, see [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username).
+1. Create an organization using your original username, then follow the steps below to move your work.
+
+## Moving your work to an organization
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.organizations %}
+1. Under the "Move to an organization" section, click **Move work to an organization**.
+1. Follow the prompts to transfer any of your repositories and projects to a new or existing organization. {% ifversion fpt or ghec %}For more information about the plans available for your team, see [AUTOTITLE](/get-started/learning-about-github/githubs-plans).{% endif %}
+1. Once done assigning your work to its new location, click **Move to an organization**, then click **Go to your organization**.
+
+## Further reading
+
+- [AUTOTITLE](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)
+- [AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)

content/copilot/concepts/prompting/response-customization.md

@@ -48,8 +48,6 @@ You can use three types of repository custom instructions in {% data variables.p
 
 {% data reusables.copilot.custom-instructions-about %}
 
-{% data reusables.copilot.repository-custom-instructions-support %}
-
 ## About organization custom instructions
 
 {% data reusables.copilot.custom-instructions-org-support %}
@@ -71,7 +69,7 @@ The following list shows the complete order of precedence, with instructions hig
 
 * **Personal** instructions
 * **Repository** custom instructions:
-  * **Path-specific** instructions in any applicable `.github/instructions/**/NAME.instructions.md` file
+  * **Path-specific** instructions in any applicable `.github/instructions/**/*.instructions.md` file
   * **Repository-wide** instructions in the `.github/copilot-instructions.md` file
   * **Agent** instructions (for example, in an `AGENTS.md` file)
 * **Organization** custom instructions
@@ -132,8 +130,6 @@ You can use three types of repository custom instructions in {% data variables.p
 
 {% data reusables.copilot.custom-instructions-about %}
 
-{% data reusables.copilot.repository-custom-instructions-support %}
-
 ## About prompt files
 
 > [!NOTE] Prompt files are {% data variables.release-phases.public_preview %} and subject to change.
@@ -225,16 +221,14 @@ You can use two types of repository custom instructions in {% data variables.pro
 
 * **Path-specific custom instructions**, which apply to requests made in the context of files that match a specified path.
 
-  These are specified in one or more `NAME.instructions.md` files within the `.github/instructions` directory in the repository.
+  These are specified in one or more `NAME.instructions.md` files within or below the `.github/instructions` directory in the repository.
 
   By using path-specific instructions you can avoid overloading your repository-wide instructions with information that only applies to files of certain types, or in certain directories.
 
-See the table below for details of support for each of these types of repository custom instructions across different {% data variables.product.prodname_copilot_short %} features.
+For details of support for each of these types of repository custom instructions across different {% data variables.product.prodname_copilot_short %} features, see [AUTOTITLE](/copilot/reference/custom-instructions-support).
 
 For a curated collection of examples, see [AUTOTITLE](/copilot/tutorials/customization-library/custom-instructions).
 
-{% data reusables.copilot.repository-custom-instructions-support %}
-
 ## About prompt files
 
 Prompt files let you build and share reusable prompt instructions with additional context. A prompt file is a Markdown file, stored in your workspace, that mimics the existing format of writing prompts in {% data variables.copilot.copilot_chat_short %} (for example, `Rewrite #file:x.ts`). This allows blending natural language instructions, additional context, and even linking to other prompt files as dependencies.
@@ -317,7 +311,9 @@ While custom instructions help to add codebase-wide context to each AI workflow,
 
 In JetBrains IDEs, repository custom instructions consist of a single file, `.github/copilot-instructions.md`, that you create in a repository. The instructions you add to the file should be short, self-contained statements that add context or relevant information to supplement a {% data variables.product.prodname_copilot_short %} prompt.
 
-{% data reusables.copilot.repository-custom-instructions-support %}
+### Support for repository custom instructions
+
+For details of which types of custom instructions are supported across various environments, see [AUTOTITLE](/copilot/reference/custom-instructions-support).
 
 ### Use cases for custom instructions
 
@@ -411,7 +407,9 @@ For a curated collection of examples, see [AUTOTITLE](/copilot/tutorials/customi
 
 In Xcode, repository custom instructions consist of a single file, `.github/copilot-instructions.md`, that you create in a repository. The instructions you add to the file should be short, self-contained statements that add context or relevant information to supplement a {% data variables.product.prodname_copilot_short %} prompt.
 
-{% data reusables.copilot.repository-custom-instructions-support %}
+### Support for repository custom instructions
+
+For details of which types of custom instructions are supported across various environments, see [AUTOTITLE](/copilot/reference/custom-instructions-support).
 
 ### Use cases for custom instructions
 

content/copilot/how-tos/configure-custom-instructions/add-repository-instructions.md

@@ -217,7 +217,7 @@ Once saved, these instructions will apply to the current project in Eclipse that
 
 * **Path-specific custom instructions**, which apply to requests made in the context of files that match a specified path.
 
-  These are specified in one or more `NAME.instructions.md` files within the `.github/instructions` directory in the repository. See [Creating path-specific custom instructions](#creating-path-specific-custom-instructions).
+  These are specified in one or more `NAME.instructions.md` files within or below the `.github/instructions` directory in the repository. See [Creating path-specific custom instructions](#creating-path-specific-custom-instructions).
 
   If the path you specify matches a file that {% data variables.product.prodname_copilot_short %} is working on, and a repository-wide custom instructions file also exists, then the instructions from both files are used. You should avoid potential conflicts between instructions as {% data variables.product.prodname_copilot_short %}'s choice between conflicting instructions is non-deterministic.
 
@@ -253,7 +253,7 @@ Once saved, these instructions will apply to the current project in Eclipse that
 
 * **Path-specific custom instructions**, which apply to requests made in the context of files that match a specified path.
 
-  These are specified in one or more `NAME.instructions.md` files within the `.github/instructions` directory in the repository. See [Creating path-specific custom instructions](#creating-path-specific-custom-instructions-1).
+  These are specified in one or more `NAME.instructions.md` files within or below the `.github/instructions` directory in the repository. See [Creating path-specific custom instructions](#creating-path-specific-custom-instructions-1).
 
   If the path you specify matches a file that {% data variables.product.prodname_copilot_short %} is working on, and a repository-wide custom instructions file also exists, then the instructions from both files are used.
 
@@ -290,7 +290,7 @@ Once saved, these instructions will apply to the current project in Eclipse that
 
 * **Path-specific custom instructions**, which apply to requests made in the context of files that match a specified path.
 
-  These are specified in one or more `NAME.instructions.md` files within the `.github/instructions` directory in the repository. See [Creating path-specific custom instructions](#creating-path-specific-custom-instructions-2).
+  These are specified in one or more `NAME.instructions.md` files within or below the `.github/instructions` directory in the repository. See [Creating path-specific custom instructions](#creating-path-specific-custom-instructions-2).
 
   If the path you specify matches a file that {% data variables.product.prodname_copilot_short %} is working on, and a repository-wide custom instructions file also exists, then the instructions from both files are used.
 
@@ -320,7 +320,7 @@ Once saved, these instructions will apply to the current project in Eclipse that
 
 * **Path-specific custom instructions** apply to requests made in the context of files that match a specified path.
 
-  These are specified in one or more `NAME.instructions.md` files within the `.github/instructions` directory in the repository. See [Creating path-specific custom instructions](#creating-path-specific-custom-instructions-2).
+  These are specified in one or more `NAME.instructions.md` files within or below the `.github/instructions` directory in the repository. See [Creating path-specific custom instructions](#creating-path-specific-custom-instructions-2).
 
   If the path you specify matches a file that {% data variables.product.prodname_copilot_short %} is working on, and a repository-wide custom instructions file also exists, then the instructions from both files are used.
 

content/copilot/how-tos/use-copilot-agents/use-copilot-cli.md

@@ -11,7 +11,7 @@ topics:
   - Copilot
   - CLI
 contentType: how-tos
-category: 
+category:
   - Author and optimize with Copilot
 ---
 
@@ -171,7 +171,7 @@ You can enhance {% data variables.product.prodname_copilot_short %}’s performa
 {% data variables.copilot.copilot_cli_short %} supports:
 
 * Repository-wide instructions in the `.github/copilot-instructions.md` file.
-* Path-specific instructions files: `.github/copilot-instructions/**/*.instructions.md`.
+* Path-specific instructions files: `.github/instructions/**/*.instructions.md`.
 * Agent files such as `AGENTS.md`.
 
 For more information, see [AUTOTITLE](/copilot/how-tos/configure-custom-instructions/add-repository-instructions).
@@ -201,11 +201,11 @@ In the case of naming conflicts, a system-level agent overrides a repository-lev
 * Calling out to {% data variables.copilot.copilot_custom_agent_short %} directly in a prompt:
 
   ```shell
-  Use the refactoring agent to refactor this code block 
+  Use the refactoring agent to refactor this code block
   ```
 
   {% data variables.product.prodname_copilot_short %} will automatically infer the agent you want to use.
-  
+
 * Specifying the {% data variables.copilot.copilot_custom_agent_short %} you want to use with the command-line option. For example:
 
   ```shell