Merge pull request #39829 from github/repo-sync

Repo sync

Author: docs-bot

content/code-security/secret-scanning/introduction/about-push-protection.md

@@ -47,12 +47,13 @@ Push protection has some limitations. For more information, see [AUTOTITLE](/cod
 
 ## How push protection works
 
-Push protection works:
+Push protection blocks secrets detected in:
 
-* From the command line. See [AUTOTITLE](/code-security/secret-scanning/working-with-secret-scanning-and-push-protection/working-with-push-protection-from-the-command-line).
-* In the {% data variables.product.prodname_dotcom %} UI. See [AUTOTITLE](/code-security/secret-scanning/working-with-secret-scanning-and-push-protection/working-with-push-protection-in-the-github-ui).{% ifversion push-protection-delegated-bypass-file-upload-support %}
-* On files uploaded onto the repository on {% data variables.product.prodname_dotcom %}.{% endif %}{% ifversion secret-scanning-push-protection-content-endpoints %}
-* From the REST API. See [AUTOTITLE](/code-security/secret-scanning/working-with-secret-scanning-and-push-protection/working-with-push-protection-from-the-rest-api).{% endif %}
+* Pushes from the command line. See [AUTOTITLE](/code-security/secret-scanning/working-with-secret-scanning-and-push-protection/working-with-push-protection-from-the-command-line).
+* Commits made in the {% data variables.product.prodname_dotcom %} UI. See [AUTOTITLE](/code-security/secret-scanning/working-with-secret-scanning-and-push-protection/working-with-push-protection-in-the-github-ui).{% ifversion push-protection-delegated-bypass-file-upload-support %}
+* File uploads to a repository on {% data variables.product.prodname_dotcom %}.{% endif %}{% ifversion secret-scanning-push-protection-content-endpoints %}
+* Requests to the REST API. See [AUTOTITLE](/code-security/secret-scanning/working-with-secret-scanning-and-push-protection/working-with-push-protection-from-the-rest-api).{% endif %}
+* Interactions with the {% data variables.product.github %} MCP server (public repositories only). See [AUTOTITLE](/enterprise-cloud@latest/code-security/secret-scanning/working-with-secret-scanning-and-push-protection/working-with-push-protection-and-the-github-mcp-server).
 
 Once enabled, if push protection detects a potential secret during a push attempt, it will block the push and provide a detailed message explaining the reason for the block. You will need to review the code in question, remove any sensitive information, and reattempt the push.
 

content/code-security/secret-scanning/working-with-secret-scanning-and-push-protection/index.md

@@ -18,6 +18,7 @@ children:
   - /working-with-push-protection-from-the-command-line
   - /working-with-push-protection-from-the-rest-api
   - /working-with-push-protection-in-the-github-ui
+  - /working-with-push-protection-and-the-github-mcp-server
 redirect_from:
   - /code-security/secret-scanning/working-with-push-protection
   - /code-security/secret-scanning/pushing-a-branch-blocked-by-push-protection

content/code-security/secret-scanning/working-with-secret-scanning-and-push-protection/working-with-push-protection-and-the-github-mcp-server.md

@@ -0,0 +1,36 @@
+---
+title: Working with push protection and the GitHub MCP server
+shortTitle: Push protection and the GitHub MCP server
+intro: 'Learn how you are protected from leaking secrets during interactions with the {% data variables.product.github %} MCP server, and how to bypass a push protection block if you need to.'
+product: 'Public repositories on {% data variables.product.prodname_dotcom_the_website %}'
+permissions: '{% data reusables.permissions.push-protection-resolve-block %}'
+versions:
+  feature: copilot
+type: how_to
+topics:
+  - Secret scanning
+  - Secret Protection
+  - Alerts
+  - Repositories
+  - Copilot
+---
+
+## About push protection and the {% data variables.product.github %} MCP server
+
+Push protection prevents you from inadvertently exposing secrets, such as tokens, keys and credentials, in your repository.
+
+When you're interacting with the {% data variables.product.github %} MCP server, push protection blocks secrets in AI-generated responses as well as preventing secrets from being included in any actions you perform, such as creating an issue.
+
+This protection is on by default for all interactions between the {% data variables.product.github %} MCP server and **public repositories** only, regardless of whether push protection is enabled on the repository's security settings page.
+
+## Resolving a block
+
+To resolve the block, you can either:
+
+* **Remove** the secret from the content of your request before trying again.
+* **Bypass the block.** If push protection is enabled for the repository, or you have push protection enabled for your personal account, you'll see an option to bypass the push protection block. You should carefully evaluate if it's safe to include the secret in your request before continuing.
+
+## Further reading
+
+* [AUTOTITLE](/code-security/secret-scanning/introduction/about-push-protection)
+* [About the {% data variables.product.github %} MCP server](/copilot/concepts/about-mcp#about-the-github-mcp-server)

content/copilot/concepts/about-mcp.md

@@ -37,6 +37,8 @@ The {% data variables.product.github %} MCP server is a Model Context Protocol (
 * Connect third-party tools (like Cursor, Windsurf, or future integrations) to leverage {% data variables.product.github %}’s context and AI capabilities.
 * Enable cloud-based workflows that work from any device, without local setup.
 
+For public repositories, interactions with the {% data variables.product.github %} MCP server are secured by push protection, which blocks secrets from being included in AI-generated responses and prevents you from exposing secrets through any actions you perform using the server, such as creating an issue. See [AUTOTITLE](/code-security/secret-scanning/working-with-secret-scanning-and-push-protection/working-with-push-protection-and-the-github-mcp-server).
+
 You can access the {% data variables.product.github %} MCP server remotely through {% data variables.product.prodname_vscode %}, or other editors that support remote MCP; or you can run it locally in any MCP-compatible editor, allowing you to choose between the convenience of a hosted solution or the customizability of a self-hosted setup.
 
 If you want to utilize the remote {% data variables.product.github %} MCP server, you can do so in a few steps, without any local setup. This is particularly useful for users who want to quickly leverage {% data variables.product.github %}’s AI capabilities without the overhead of managing a local MCP server.

content/copilot/concepts/billing/billing-for-individuals.md

@@ -1,5 +1,5 @@
 ---
-title: About billing for individual Copilot plans
+title: About billing for individual GitHub Copilot plans
 shortTitle: Billing for individuals
 intro: 'Learn how billing works for {% data variables.copilot.copilot_pro_short %} and {% data variables.copilot.copilot_pro_plus_short %}.'
 versions:

content/copilot/concepts/billing/individual-plans.md

@@ -1,5 +1,5 @@
 ---
-title: About individual Copilot plans and benefits
+title: About individual GitHub Copilot plans and benefits
 shortTitle: Individual plans
 intro: '{% data variables.product.company_short %} offers several {% data variables.product.prodname_copilot_short %} plans for individual developers, each with different features, model access, and usage limits to support a wide range of coding needs.'
 versions:

content/copilot/concepts/billing/organizations-and-enterprises.md

@@ -44,7 +44,7 @@ If a single user receives a seat from multiple organizations in the same enterpr
 
 ## Billing cycles
 
-Billed users are calculated at the end of each billing cycle, based on the number of {% data variables.product.prodname_copilot %} seats that are assigned. You can add or remove seats at any time during the billing cycle.
+Billed users are calculated at the end of each billing cycle, based on the number of {% data variables.product.prodname_copilot %} seats that are assigned. Although you can add or remove seats at any time during the billing cycle, billing for removed seats continues until the end of the current billing cycle. See [AUTOTITLE](/copilot/reference/copilot-billing/license-changes).
 
 ## Reference
 

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

@@ -1,5 +1,5 @@
 ---
-title: About Copilot code review
+title: About GitHub Copilot code review
 shortTitle: Code review
 allowTitleToDifferFromFilename: true
 intro: 'Find out how {% data variables.product.prodname_copilot_short %} can review pull requests for you.'

content/copilot/concepts/coding-agent/coding-agent.md

@@ -1,5 +1,5 @@
 ---
-title: About Copilot coding agent
+title: About GitHub Copilot coding agent
 shortTitle: Coding agent
 intro: 'You can assign {% data variables.product.github %} issues to {% data variables.product.prodname_copilot_short %}, or ask {% data variables.product.prodname_copilot_short %} to create a pull request.'
 product: '{% data reusables.gated-features.copilot-coding-agent %}<br><a href="https://github.com/features/copilot/plans?ref_cta=Copilot+plans+signup&ref_loc=about+assigning+issues+to+copilot&ref_page=docs" target="_blank" class="btn btn-primary mt-3 mr-3 no-underline"><span>Sign up for {% data variables.product.prodname_copilot_short %}</span> {% octicon "link-external" height:16 %}</a>'

content/copilot/concepts/coding-agent/enable-coding-agent.md

@@ -1,5 +1,5 @@
 ---
-title: 'About enabling {% data variables.copilot.copilot_coding_agent %}'
+title: About enabling GitHub Copilot coding agent
 shortTitle: 'Enable {% data variables.copilot.copilot_coding_agent_short %}'
 allowTitleToDifferFromFilename: true
 intro: 'Find out about enabling {% data variables.copilot.copilot_coding_agent %} for {% data variables.copilot.copilot_enterprise %} and {% data variables.copilot.copilot_for_business %}, and about disabling the agent for specific repositories.'