Merge pull request #43110 from github/repo-sync

Repo sync

Author: docs-bot

content/admin/configuring-settings/hardening-security-for-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list.md

@@ -126,6 +126,33 @@ To ensure seamless use of the OIDC CAP while still applying the policy to OAuth
 1. Optionally, to allow installed {% data variables.product.company_short %} and {% data variables.product.prodname_oauth_apps %} to access your enterprise from any IP address, select **Skip IdP check for applications**.
 1. Click **Save**.
 
+## Restricting access to user-owned resources with the IP allow list
+
+> [!NOTE]
+> User-level IP allow list enforcement is only available for enterprises that use {% data variables.product.prodname_emus %}.
+
+By default, your enterprise's IP allow list does not restrict access to repositories and other resources owned by {% data variables.enterprise.prodname_managed_users %}. You can enable user-level enforcement to extend IP allow list restrictions to user-owned resources, including:
+
+* User-owned repositories and their forks
+* User profile pages
+
+This ensures that all locations where enterprise code may reside—not just organization-owned repositories—are only accessible from allowed IP addresses.
+
+### Enabling user-level enforcement
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.security-tab %}
+1. Under "IP allow list", select **Enable IP allow list user-level enforcement**.
+1. Click **Save**.
+
+> [!IMPORTANT]
+> Before enabling user-level enforcement, add all IP addresses that your {% data variables.enterprise.prodname_managed_users %} use to connect to the enterprise IP allow list. If a user connects from an IP address that isn’t on the allow list, they won’t be able to access their user-owned resources.
+
+### Disabling user-level enforcement
+
+To stop enforcing the IP allow list on user-owned resources, follow the same steps above and deselect **Enable IP allow list user-level enforcement**, then click **Save**. Access to user-owned resources will no longer be restricted by the IP allow list.
+
 ## Using {% data variables.product.prodname_actions %} with an IP allow list
 
 {% data reusables.actions.ip-allow-list-self-hosted-runners %}

content/code-security/how-tos/manage-security-alerts/manage-dependabot-alerts/viewing-and-updating-dependabot-alerts.md

@@ -62,12 +62,17 @@ By default, alerts are sorted by **Most important**, which helps you prioritize
 
    ![Screenshot showing the "Tags" section in the alert details page.](/assets/images/help/repository/dependabot-alerts-tags-section.png)
 
+{% ifversion dependabot-alerts-assignees %}
+1. On the right panel,  select an assignee by using the **Assignees** dropdown list. This clearly communicates who is responsible for triaging the alert so that no effort is wasted on repetitive analysis without worrying that alerts might fall through the cracks.
+{% endif %}
+
 1. Optionally, to suggest an improvement to the related security advisory, on the right-hand side of the alert details page, click **Suggest improvements for this advisory on the {% data variables.product.prodname_advisory_database %}**. See [AUTOTITLE](/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/editing-security-advisories-in-the-github-advisory-database).
 
 ### Tips for prioritizing alerts
 
 * Use the **Most important** sort order to focus on alerts with the highest potential impact.
-* Prioritize alerts that affect production dependencies over development dependencies.
+* Prioritize alerts that affect production dependencies over development dependencies.{% ifversion dependabot-alerts-assignees %}
+* Use the **Assignees** feature to clarify who is responsible for addressing each alert, so your team can track and remediate vulnerabilities more effectively.{% endif %}
 * Use {% data variables.dependabot.auto_triage_rules %} to automatically prioritize or manage alerts. See [AUTOTITLE](/code-security/concepts/supply-chain-security/about-dependabot-auto-triage-rules).
 
 For more information about supported ecosystems and manifest files for dependency scope, see [AUTOTITLE](/code-security/reference/supply-chain-security/supported-ecosystems-and-manifests-for-dependency-scope).

content/copilot/concepts/agents/about-agent-skills.md

@@ -33,3 +33,4 @@ To create an agent skill, see:
 
 * [AUTOTITLE](/copilot/how-tos/use-copilot-agents/coding-agent/create-skills)
 * [AUTOTITLE](/copilot/how-tos/copilot-cli/customize-copilot/create-skills)
+* [AUTOTITLE](/copilot/reference/customization-cheat-sheet)

content/copilot/concepts/agents/coding-agent/about-custom-agents.md

@@ -27,7 +27,7 @@ The {% data variables.copilot.agent_profile %} defines the {% data variables.cop
 * **Prompt**: Custom instructions that define the agent's behavior and expertise.
 * **Tools** (optional): Specific tools the agent can access. By default, agents can access all available tools, including built-in tools and MCP server tools.
 
-Organization and enterprise-level {% data variables.copilot.agent_profiles %} can also include MCP server configurations using the `mcp-server` property.
+{% data variables.copilot.agent_profiles_caps %} can also include MCP server configurations using the `mcp-server` property.
 
 ### Example {% data variables.copilot.agent_profile %}
 
@@ -79,3 +79,4 @@ To create your own {% data variables.copilot.custom_agents_short %}, see:
 
 * [AUTOTITLE](/copilot/how-tos/use-copilot-agents/coding-agent/create-custom-agents)
 * [AUTOTITLE](/copilot/how-tos/copilot-cli/customize-copilot/create-custom-agents-for-cli)
+* [AUTOTITLE](/copilot/reference/customization-cheat-sheet)

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

@@ -46,7 +46,7 @@ For details of how to set up MCP servers for {% data variables.copilot.copilot_c
 
 ## MCP servers for {% data variables.copilot.custom_agents_short %}
 
-Organization and enterprise administrators can also configure MCP servers as part of {% data variables.copilot.custom_agents_short %}.
+You can also configure MCP servers for {% data variables.copilot.custom_agents_short %}.
 
 MCP servers configured in {% data variables.copilot.custom_agents_short %} are available only to that specific agent and follow the same processing order as other MCP configurations, with {% data variables.copilot.copilot_custom_agent_short %} MCP settings processed after default servers but before repository-level configurations.
 

content/copilot/concepts/context/mcp.md

@@ -102,3 +102,4 @@ The {% data variables.product.github %} MCP Registry is a curated list of MCP se
 * [AUTOTITLE](/copilot/how-tos/context/model-context-protocol/extending-copilot-chat-with-mcp)
 * [AUTOTITLE](/copilot/how-tos/context/model-context-protocol/using-the-github-mcp-server)
 * [AUTOTITLE](/copilot/tutorials/enhancing-copilot-agent-mode-with-mcp)
+* [AUTOTITLE](/copilot/reference/customization-cheat-sheet)

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

@@ -104,6 +104,7 @@ Here are some common use cases and examples for each type of custom instructions
 ## Further reading
 
 * [AUTOTITLE](/copilot/concepts/agents/copilot-memory)
+* [AUTOTITLE](/copilot/reference/customization-cheat-sheet)
 
 {% endwebui %}
 
@@ -191,6 +192,7 @@ For information on how to enable, create, and use prompt files, see [AUTOTITLE](
 
 * [AUTOTITLE](/copilot/customizing-copilot/adding-repository-custom-instructions-for-github-copilot)
 * [AUTOTITLE](/copilot/tutorials/use-custom-instructions)
+* [AUTOTITLE](/copilot/reference/customization-cheat-sheet)
 
 {% endvscode %}
 
@@ -287,6 +289,7 @@ For information on how to create and use prompt files, see [AUTOTITLE](/copilot/
 ## Next steps
 
 * [AUTOTITLE](/copilot/customizing-copilot/adding-repository-custom-instructions-for-github-copilot)
+* [AUTOTITLE](/copilot/reference/customization-cheat-sheet)
 
 {% endvisualstudio %}
 
@@ -390,6 +393,7 @@ For a curated collection of examples, see [AUTOTITLE](/copilot/tutorials/customi
 
 * [AUTOTITLE](/copilot/customizing-copilot/adding-repository-custom-instructions-for-github-copilot)
 * [AUTOTITLE](/copilot/tutorials/use-custom-instructions)
+* [AUTOTITLE](/copilot/reference/customization-cheat-sheet)
 
 {% endjetbrains %}
 
@@ -435,6 +439,7 @@ For a curated collection of examples, see [AUTOTITLE](/copilot/tutorials/customi
 
 * [AUTOTITLE](/copilot/customizing-copilot/adding-repository-custom-instructions-for-github-copilot)
 * [AUTOTITLE](/copilot/tutorials/use-custom-instructions)
+* [AUTOTITLE](/copilot/reference/customization-cheat-sheet)
 
 {% endxcode %}
 
@@ -481,6 +486,7 @@ For a curated collection of examples, see [AUTOTITLE](/copilot/tutorials/customi
 
 * [AUTOTITLE](/copilot/customizing-copilot/adding-repository-custom-instructions-for-github-copilot)
 * [AUTOTITLE](/copilot/tutorials/use-custom-instructions)
+* [AUTOTITLE](/copilot/reference/customization-cheat-sheet)
 
 {% endeclipse %}
 

content/copilot/how-tos/use-copilot-agents/coding-agent/create-custom-agents.md

@@ -80,16 +80,16 @@ To update an {% data variables.copilot.agent_profile %}, from the agents dropdow
 
 ## Configuring an {% data variables.copilot.agent_profile %}
 
-An {% data variables.copilot.agent_profile %} is a Markdown file with YAML frontmatter that specifies the {% data variables.copilot.copilot_custom_agent_short %}'s name, description, available tools, and MCP server configurations (for organization/enterprise level agents). Configuring an {% data variables.copilot.agent_profile %} involves defining the agent's identity, capabilities, tool access, and behavioral instructions.
+An {% data variables.copilot.agent_profile %} is a Markdown file with YAML frontmatter that specifies the {% data variables.copilot.copilot_custom_agent_short %}'s name, description, available tools, and MCP server configurations. Configuring an {% data variables.copilot.agent_profile %} involves defining the agent's identity, capabilities, tool access, and behavioral instructions.
 
 For detailed configuration information about YAML properties, tools, MCP server setup, tool aliases, and how {% data variables.copilot.custom_agents_short %} are processed, see [AUTOTITLE](/copilot/reference/custom-agents-configuration).
 
 To configure your {% data variables.copilot.agent_profile %}:
 
 1. Optionally, write a `name` for your {% data variables.copilot.copilot_custom_agent_short %}. If unset, the name will default to the filename (without the `.md` or `.agent.md` suffix).
 1. Write a brief `description` (required) explaining what your agent does and its specific capabilities or domain expertise.
-1. In the `tools` property, define which tools the agent can use. This is a list of tool names or aliases, including tools from MCP servers configured in the repository settings or the {% data variables.copilot.agent_profile %} (for example, `tools: ["read", "edit", "search", "some-mcp-server/tool-1"]`). If you omit this property, the agent will have access to all available tools.
-1. If creating an organization or enterprise level agent on {% data variables.product.github %}, you can use the `mcp-servers` property to optionally configure MCP servers that will be available only to this agent to extend its capabilities.
+1. In the `tools` property, define which tools the agent can use. This is a list of tool names or aliases, including tools from MCP servers configured in the repository settings or the {% data variables.copilot.agent_profile %} (for example, `tools: ["read", "edit", "search", "some-mcp-server/tool-1"]`). If you omit this property, the agent will have access to all available tools. See "Tools" in [AUTOTITLE](/copilot/reference/custom-agents-configuration#tools).
+1. Optionally, in the `mcp-servers` property, you can configure MCP servers that will be available only to this agent to extend its capabilities. See "MCP server configuration details" in [AUTOTITLE](/copilot/reference/custom-agents-configuration#mcp-server-configuration-details). 
 1. If you are creating and using the {% data variables.copilot.agent_profile %} in {% data variables.product.prodname_vscode_shortname %}, JetBrains IDEs, Eclipse, or Xcode, you can also use the `model` property to control which AI model the agent should use.
 1. Optionally, set the `target` property to either `vscode` or `github-copilot` if you want to only use the agent in a specific environment. The agent will be available in both environments if you omit the property.
 1. Write the agent's prompt. Define the agent's behavior, expertise, and instructions in the Markdown content below the YAML frontmatter. The prompt can be a maximum of 30,000 characters.

content/copilot/reference/cheat-sheet.md …nt/copilot/reference/chat-cheat-sheet.mdcontent/copilot/reference/cheat-sheet.md renamed to content/copilot/reference/chat-cheat-sheet.md content/copilot/reference/cheat-sheet.md renamed to content/copilot/reference/chat-cheat-sheet.md

@@ -1,6 +1,6 @@
 ---
 title: GitHub Copilot Chat cheat sheet
-shortTitle: Cheat sheet
+shortTitle: Chat cheat sheet
 intro: 'Use this cheat sheet to quickly reference the most common commands and options for using {% data variables.copilot.copilot_chat %}.'
 versions:
   feature: copilot
@@ -9,6 +9,7 @@ topics:
 category:
   - Author and optimize with Copilot
 redirect_from:
+  - /copilot/reference/cheat-sheet
   - /copilot/using-github-copilot/github-copilot-chat-cheat-sheet
   - /copilot/using-github-copilot/copilot-chat/github-copilot-chat-cheat-sheet
   - /copilot/reference/github-copilot-chat-cheat-sheet