Merge pull request #42762 from github/repo-sync

Repo sync

Author: docs-bot

content/copilot/concepts/agents/code-review.md

@@ -17,13 +17,16 @@ category:
 
 {% data reusables.copilot.personal-instructions-note %}
 
-For an overview of the methods you can use to customize {% data variables.copilot.copilot_chat %} responses, see [AUTOTITLE](/copilot/concepts/about-customizing-github-copilot-chat-responses?tool=webui).
+You can customize {% data variables.copilot.copilot_chat %} responses in several ways. For an overview, see [AUTOTITLE](/copilot/concepts/about-customizing-github-copilot-chat-responses?tool=webui).
 
-## About personal custom instructions for {% data variables.copilot.copilot_chat %}
+## About personal custom instructions for {% data variables.copilot.copilot_chat_short %}
+
+Add custom instructions to receive personalized chat responses. Your instructions apply to all your conversations on the {% data variables.product.github %} website. Custom instructions let you specify preferences such as your preferred language or response style. 
+
+Examples of instructions you can add:
 
-You can add custom instructions for {% data variables.copilot.copilot_chat %} in order to receive chat responses that are customized to your personal preferences, across your conversations on the {% data variables.product.github %} website. For example, you can choose to always have {% data variables.copilot.copilot_chat_short %} respond in a preferred language or with a particular style. Some examples of instructions you could add are:
 * `Always respond in Spanish.`
-* `Your style is a helpful colleague, minimize explanations but provide enough context to understand the code.`
+* `Use a helpful, collegial tone. Keep explanations brief, but provide enough context to understand the code.`
 * `Always provide examples in TypeScript.`
 
 > [!NOTE]
@@ -32,15 +35,20 @@ You can add custom instructions for {% data variables.copilot.copilot_chat %} in
 
 ## Adding personal custom instructions
 
-You can add personal custom instructions in {% data variables.copilot.copilot_chat_short %} in {% data variables.product.github %}.
+To add personal custom instructions in {% data variables.copilot.copilot_chat_short %} on {% data variables.product.github %}:
 
 1. Open [{% data variables.copilot.copilot_chat_short %}](https://github.com/copilot?ref_product=copilot&ref_type=engagement&ref_style=text).
-1. In the bottom left corner, click your profile picture, then click **{% octicon "note" aria-hidden="true" aria-label="note" %} Personal instructions**.
+1. In the bottom left corner, click your profile picture. Then click **{% octicon "note" aria-hidden="true" aria-label="note" %} Personal instructions**.
 1. Add natural language instructions to the text box.
+  
+   Use any format. For example, a single block of text, each instruction on a new line, or instructions separated by blank lines.
+
+1. Optionally, use a template for common instructions. Click {% octicon "light-bulb" aria-label="The light-bulb icon" %} and select a template. 
+
+   When you select a template, placeholder text appears. Replace placeholders like `{format}` with your preferences.
+1. Click **Save**.
 
-   You can write your instructions in any format you prefer. For example, you can write them as a single block of text, each on a new line, or separated by blank lines.
-1. Optionally, click {% octicon "light-bulb" aria-label="The light-bulb icon" %} to view templates you can use for common instructions. If you click on one of the boxes, such as "Communication", instructions will be added to the text box with placeholders, such as `{format}` that you can replace with your preferences.
-1. Click **Save**. Your instructions are now active, and will stay active until you change or remove them.
+Your instructions are now active. They will remain active until you change or remove them.
 
 {% note %}
 

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

@@ -16,22 +16,26 @@ category:
   - Author and optimize with Copilot
 ---
 
-If you're starting a new feature, trying to understand a system, or picking up a task in a codebase you’re still learning, {% data variables.copilot.copilot_spaces %} can help you:
+{% data variables.copilot.copilot_spaces %} helps you work faster when starting a new feature, understanding a system, or picking up a task in an unfamiliar codebase.
 
-* Stay focused by organizing the context you need in one place.
-* Get better help from {% data variables.product.prodname_copilot_short %} by grounding it in relevant code and documentation.
-* Move faster without switching between tools or asking others for background information.
+Use {% data variables.copilot.copilot_spaces_short %} to:
+
+* Organize the context you need in one place.
+* Provide {% data variables.product.prodname_copilot_short %} with relevant code and documentation.
+* Reduce time spent switching between tools or asking others for background information.
 
 To create a space, go to [https://github.com/copilot/spaces](https://github.com/copilot/spaces?ref_product=copilot&ref_type=engagement&ref_style=text), and click **Create space**.
 
-Below are some examples of how to use {% data variables.copilot.copilot_spaces_short %} to help you with development work.
+The examples in this article show you how to use {% data variables.copilot.copilot_spaces_short %} for common development tasks.
 
 ## 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 mockup images. {% data variables.product.prodname_copilot_short %} can help you:
+Create a space when you start working on a specific feature. Add the relevant code, a product specification, and any supporting materials. Supporting materials can include 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.
+* Suggest changes or additions based on the specification.
 * Draft a first implementation or outline next steps.
 * Flag missing elements or inconsistencies.
 
@@ -43,12 +47,14 @@ 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. 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:
+Document the logic for repetitive tasks once and share it through a space. This approach keeps everyone consistent and saves time. Tasks like tracking telemetry events or handling event emissions benefit from this approach.
+
+If you have a process flowchart, upload it to your space for reference. {% data variables.product.prodname_copilot_short %} can:
 
-* Suggesting efficient patterns based on your previous work.
-* Helping write reusable functions or templates.
-* Reviewing the logic to ensure it aligns with project standards.
-* Providing examples of how similar tasks have been handled in the codebase.
+* Suggest efficient patterns based on your previous work.
+* Help write reusable functions or templates.
+* Review the logic to ensure it aligns with project standards.
+* Provide examples of how similar tasks have been handled in the codebase.
 
 **Instructions**:
 > You help developers implement telemetry events. You should (1) validate what the user's goals are for the event, (2) propose a new event structure based on examples of existing events (and using the common telemetry schema), and (3) create a new version of the telemetry config file.
@@ -58,11 +64,13 @@ When working on repetitive tasks like tracking telemetry events or handling even
 
 ## Sharing knowledge with teammates
 
-In situations where people tend to ask similar questions, such as how authentication or search works in your project, {% data variables.product.prodname_copilot_short %} can help:
+Create a space for topics where people tend to ask similar questions. For example, questions about how authentication or search works in your project.
+
+{% data variables.product.prodname_copilot_short %} can:
 
 * Explain how the code works.
-* Answer questions grounded in the latest documentation.
-* Guide new team members on the best practices.
+* Answer questions based on the latest documentation.
+* Guide new team members on best practices.
 
 **Instructions**:
 > You contain the code and documentation associated with our authentication system.
@@ -72,16 +80,17 @@ In situations where people tend to ask similar questions, such as how authentica
 
 ## Hands-on practice
 
-Try the [Scale institutional knowledge using Copilot Spaces](https://github.com/skills/scale-institutional-knowledge-using-copilot-spaces) Skills exercise for practical experience to do the following:
-* Centralize scattered project management knowledge in Copilot Spaces
-* Convert tacit team insights into searchable, versioned artifacts
-* Give all team members equal access to processes, decisions, and rationale
-* Connect a repository as a structured knowledge source
-* Extract, refine, and standardize workflows collaboratively
-* Feed validated improvements back into living documentation
-* Accelerate onboarding and reduce single-person dependency risk
-* Enable consistent, repeatable project execution
+Try the [Scale institutional knowledge using Copilot Spaces](https://github.com/skills/scale-institutional-knowledge-using-copilot-spaces) Skills exercise for practical experience. This exercise shows you how to:
+
+* Centralize scattered project management knowledge in Copilot Spaces.
+* Convert team insights into searchable, versioned artifacts.
+* Give all team members equal access to processes, decisions, and rationale.
+* Connect a repository as a structured knowledge source.
+* Extract, refine, and standardize workflows collaboratively.
+* Feed validated improvements back into living documentation.
+* Accelerate onboarding and reduce single-person dependency risk.
+* Enable consistent, repeatable project execution.
 
 ## Next steps
 
-Once you’ve created a space to help with development tasks, consider sharing it with your team to reduce handoffs and repeated questions. See [AUTOTITLE](/copilot/using-github-copilot/copilot-spaces/collaborating-with-your-team-using-copilot-spaces).
+After you create a space to help with development tasks, consider sharing it with your team to reduce handoffs and repeated questions. See [AUTOTITLE](/copilot/using-github-copilot/copilot-spaces/collaborating-with-your-team-using-copilot-spaces).

content/copilot/tutorials/speed-up-development-work.md

@@ -20,7 +20,7 @@ topics:
 Deleting a public repository will not delete any forks of the repository.
 
 > [!WARNING]
-> * Deleting a repository will **permanently** delete release attachments and team permissions. This action **cannot** be undone.
+> * Deleting a repository will **permanently** delete team permissions. This action **cannot** be undone.
 > * Deleting a private{% ifversion ghes or ghec %} or internal{% endif %} repository will delete all forks of the repository.
 
 Some deleted repositories can be restored within 90 days of deletion. {% ifversion ghes %}Your site administrator may be able to restore a deleted repository for you. For more information, see [AUTOTITLE](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository). {% else %}For more information, see [AUTOTITLE](/repositories/creating-and-managing-repositories/restoring-a-deleted-repository).{% endif %}

content/repositories/creating-and-managing-repositories/deleting-a-repository.md

@@ -36,7 +36,7 @@ If you want to restore a repository that was part of a fork network that is not
 
 It can take up to an hour after a repository is deleted before that repository is available for restoration.
 
-Restoring a repository will not restore release attachments or team permissions. Issues that are restored will not be labeled.
+Restoring a repository will not restore team permissions. Issues that are restored will not be labeled.
 
 ## Restoring a deleted repository that was owned by a personal account
 

content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md

@@ -1 +1 @@
-Multiple types of custom instructions can apply to a request sent to {% data variables.product.prodname_copilot_short %}. Personal instructions take the highest priority, followed by repository instructions, with organization instructions prioritized last. However, all sets of relevant instructions are still combined and provided to {% data variables.product.prodname_copilot_short %}.
+Multiple types of custom instructions can apply to a request sent to {% data variables.product.prodname_copilot_short %}. Personal instructions take the highest priority. Repository instructions come next, and then organization instructions are prioritized last. However, all sets of relevant instructions are provided to {% data variables.product.prodname_copilot_short %}.

data/reusables/copilot/custom-instructions-chat-precedence.md

@@ -1 +1 @@
-Whenever possible, you should avoid providing conflicting sets of instructions. If you are concerned about response quality, you can also choose to temporarily disable repository instructions. See [AUTOTITLE](/copilot/customizing-copilot/adding-repository-custom-instructions-for-github-copilot?tool=webui#enabling-or-disabling-repository-custom-instructions).
+Whenever possible, try to avoid providing conflicting sets of instructions. If you are concerned about response quality, you can temporarily disable repository instructions. See [AUTOTITLE](/copilot/customizing-copilot/adding-repository-custom-instructions-for-github-copilot?tool=webui#enabling-or-disabling-repository-custom-instructions).

data/reusables/copilot/custom-instructions-conflict.md

@@ -1 +1 @@
-> [!NOTE] Personal custom instructions are currently only supported for {% data variables.copilot.copilot_chat_dotcom %}.
+> [!NOTE] Personal custom instructions are only supported for {% data variables.copilot.copilot_chat_dotcom %}.