Merge pull request #45639 from github/repo-sync

Repo sync

Author: docs-bot

.github/workflows/triage-unallowed-contributions.yml

@@ -40,13 +40,13 @@ jobs:
           filters: 'src/workflows/unallowed-contribution-filters.yml'
 
       - name: Set up Node and dependencies
-        if: ${{ steps.filter.outputs.notAllowed || steps.filter.outputs.contentTypes}}
+        if: ${{ steps.filter.outputs.notAllowed == 'true' || steps.filter.outputs.contentTypes == 'true' }}
         uses: ./.github/actions/node-npm-setup
 
       # When there are changes to files we can't accept, leave a comment
-      # explaining this to the PR author
+      # explaining this to the PR author, and why their PR will close
       - name: "Comment about changes we can't accept"
-        if: ${{ steps.filter.outputs.notAllowed || steps.filter.outputs.contentTypes}}
+        if: ${{ steps.filter.outputs.notAllowed == 'true' || steps.filter.outputs.contentTypes == 'true' }}
         run: npm run unallowed-contributions
         env:
           REPO_OWNER_AND_NAME: ${{ github.repository }}

content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md

@@ -12,7 +12,9 @@ category:
   - Block users and report abuse
 ---
 
-You can block non-members from within your organization's settings or from a specific comment made by a user. When you block a user in a comment, you can choose to send the user a notification explaining that they were blocked and why. Otherwise, the user is not directly notified that you've blocked them. Blocked users can still delete their existing content.
+You can block non-members from within your organization's settings or from content in the organization's repositories.
+
+When you block a user from a comment, you can choose to send the user a notification explaining that they were blocked and why. Otherwise, the user is not directly notified that you've blocked them. Blocked users can still delete their existing content.
 
 {% data reusables.organizations.blocking-a-user %}
 
@@ -26,6 +28,7 @@ At the time that you block a user from your organization:
 * The user is removed as a collaborator on your organization's repositories
 * The user's contributions to your organization's repositories are no longer counted as contributions for them
 * Any pending repository or organization invitations to the blocked user are canceled
+* The user's comments on repository security advisories are hidden
 
 After you've blocked a user from your organization, they cannot:
 * Cross-reference your organization's repositories in comments
@@ -35,12 +38,17 @@ In your organization's repositories, blocked users also cannot:
 * Open issues
 * Send, close, or merge pull requests
 * Comment on issues, pull requests, or commits
+* Comment on repository security advisories
 * Add or edit wiki pages
 
-## Blocking a user in a comment
+Blocking a user from a comment doesn't delete the original issue, pull request, or security advisory.
 
-1. Navigate to the comment whose author you would like to block.
-1. In the upper-right corner of the comment, click {% octicon "kebab-horizontal" aria-label="Show options" %}, then click **Block user**.
+## Blocking a user from repository content
+
+You must be an organization owner or moderator to block a user from a repository security advisory.
+
+1. Navigate to the issue, pull request, or repository security advisory that contains the description or comment whose author you would like to block.
+1. In the upper-right corner of the description or comment, click {% octicon "kebab-horizontal" aria-label="Show options" %}, then click **Block user**.
 
    ![Screenshot of a pull request comment by octo-user. Below an icon of three dots, a dropdown menu is expanded, and "Block user" is outlined in orange.](/assets/images/help/repository/comment-menu-block-user.png)
 

content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account.md

@@ -14,7 +14,9 @@ category:
 
 ## About blocking users
 
-You can block a user in your account settings, from the user's profile, or from an issue or pull request in a repository you own. {% data variables.product.prodname_dotcom %} will not notify the user when you block them. If you want to avoid contributing to the same project as someone you've blocked, you can choose to display a warning on any repositories with prior contributions from a blocked user. For more information, see [Blocking a user in your account settings](#blocking-a-user-in-your-account-settings). You may still see the activity of blocked users in shared spaces and blocked users can delete their existing content.
+You can block a user in your account settings, from the user's profile, or from content in a repository you own.
+
+{% data variables.product.github %} will not notify the user when you block them. If you want to avoid contributing to the same project as someone you've blocked, you can choose to display a warning on any repositories with prior contributions from a blocked user. For more information, see [Blocking a user in your account settings](#blocking-a-user-in-your-account-settings). You may still see the activity of blocked users in shared spaces and blocked users can delete their existing content.
 
 > [!TIP]
 > If you're blocking a user because of a heated conversation, consider locking the conversation so only collaborators can comment. For more information, see [AUTOTITLE](/communities/moderating-comments-and-conversations/locking-conversations).
@@ -32,6 +34,7 @@ When you block a user:
 * Any pending repository or account successor invitations to or from the blocked user are canceled
 * The user is removed as a collaborator from all the projects owned by you
 * You are removed as a collaborator from all the projects owned by the user
+* The user's comments on repository security advisories are hidden
 
 After you've blocked a user, they cannot:
 * Send you any notifications, including by [@mentioning](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#mentioning-people-and-teams) your username
@@ -51,11 +54,16 @@ In repositories you own, blocked users also cannot:
 * Open issues
 * Send, close, or merge pull requests
 * Comment on issues, pull requests, or commits
+* Comment on repository security advisories
 * Add or edit wiki pages
 
-## Blocking a user in an issue or pull request
+Blocking a user from a comment doesn't delete the original issue, pull request, or security advisory.
+
+## Blocking a user in an issue, pull request, or repository security advisory
+
+You must own the repository to block a user from its content.
 
-1. Navigate to an issue or pull request in a repository you own.
+1. Navigate to the issue, pull request, or repository security advisory that contains the description or comment whose author you would like to block.
 1. In the upper-right corner of the description or comment whose author you would like to block, click {% octicon "kebab-horizontal" aria-label="Show options" %}, then click **Block user**.
 1. Optionally, add a note to describe why you blocked the user. The note will only be visible to you.
 1. To confirm, click **Block user**.

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

@@ -57,7 +57,13 @@ If a user receives a seat from multiple organizations in the same enterprise, th
 
 ## 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. 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).
+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.
+
+When you add seats, you will be billed pro rata for those seats for the rest of the billing cycle. Included {% data variables.product.prodname_ai_credits_short %} for the seats may also be prorated.
+
+When you remove seats, billing for those seats continues until the end of the current billing cycle.
+
+For more information, see [AUTOTITLE](/copilot/reference/copilot-billing/license-changes).
 
 ## Managing costs
 

content/copilot/reference/copilot-billing/license-changes.md

@@ -67,7 +67,7 @@ What you need to know about the following actions:
 
 ### Adding seats
 
-* **Billing:** Additional seats are billed on a prorated basis for the remainder of the current billing cycle.
+* **Billing:** Additional seats are billed on a prorated basis for the remainder of the current billing cycle. Included {% data variables.product.prodname_ai_credits_short %} may also be prorated.
 * **Access:** Assigned users gain **immediate access** to {% data variables.product.prodname_copilot_short %}.
 
 ### Removing seats
@@ -88,7 +88,7 @@ Additionally:
 
 ## In summary
 
-* **Proration:** Applies when adding seats/licenses or upgrading plans. You pay only for the portion of the billing cycle remaining.
+* **Proration:** Applies when adding seats/licenses or upgrading plans. You pay only for the portion of the billing cycle remaining. Included {% data variables.product.prodname_ai_credits_short %} may also be prorated.
 * **Access:** Assignments and upgrades are effective immediately for affected users. Downgrades take effect at the end of the billing cycle.
 * **Removing or canceling:** No refunds are issued for unused time; access continues until the end of the cycle paid for, unless a seat/license is revoked.
 

data/release-notes/enterprise-server/3-20/6.yml

@@ -93,3 +93,5 @@ sections:
       When applying an enterprise security configuration to all repositories (for example, enabling secret scanning or code scanning across all repositories), the system immediately enqueues enablement jobs for every organization in the enterprise simultaneously. For enterprises with a large number of repositories, this can result in significant system load and potential performance degradation. If you manage a large enterprise with many organizations and repositories, we recommend applying security configurations at the organization level rather than at the enterprise level in the UI. This allows you to enable security features incrementally and monitor system performance as you roll out changes.
     - |
       On instances with multiple Git storage nodes in a voting configuration, including cluster and geo-replication high availability topologies, upgrading may fail to correctly install Actions that ship with the new version. In some cases, previous versions of these Actions remain on the instance. To resolve this issue, run the following commands on the primary node: `ghe-config --unset 'app.actions.actions-repos-sha1sum'`, `ghe-config-apply`, and `/usr/local/share/enterprise/ghe-run-init-actions-graph`.
+    - |
+      When restoring an instance with `ghe-restore` while the replication controller is enabled, the storage directory is not restored.  [Updated: 2026-08-27]

data/release-notes/enterprise-server/3-21/4.yml

@@ -92,3 +92,5 @@ sections:
       When applying an enterprise security configuration to all repositories (for example, enabling secret scanning or code scanning across all repositories), the system immediately enqueues enablement jobs for every organization in the enterprise simultaneously. For enterprises with a large number of repositories, this can result in significant system load and potential performance degradation. If you manage a large enterprise with many organizations and repositories, we recommend applying security configurations at the organization level rather than at the enterprise level in the UI. This allows you to enable security features incrementally and monitor system performance as you roll out changes.
     - |
       On instances with multiple Git storage nodes in a voting configuration, including cluster and geo-replication high availability topologies, upgrading may fail to correctly install Actions that ship with the new version. In some cases, previous versions of these Actions remain on the instance. To resolve this issue, run the following commands on the primary node: `ghe-config --unset 'app.actions.actions-repos-sha1sum'`, `ghe-config-apply`, and `/usr/local/share/enterprise/ghe-run-init-actions-graph`.
+    - |
+      When restoring an instance with `ghe-restore` while the replication controller is enabled, the storage directory is not restored. [Updated: 2026-08-27]