Repo sync

.github/workflows/awaiting-review-label-message.yml

@@ -0,0 +1,25 @@
+name: Awaiting Review reminder label message
+
+# docs-internal mirrors workflows to github/docs, so send this reminder only in the public repo.
+on:
+  # pull_request_target lets forked PRs receive the reminder.
+  pull_request_target:
+    types: [labeled]
+
+jobs:
+  comment-on-pr:
+    if: github.repository == 'github/docs' && github.event.label.name == 'awaiting-review-reminder'
+    runs-on: ubuntu-latest
+    permissions:
+      pull-requests: write
+    steps:
+      - name: Comment with contribution guidance
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          PR_URL: ${{ github.event.pull_request.html_url }}
+        run: |
+          gh pr comment "$PR_URL" --body-file - <<'EOF'
+          Please do not open pull requests to address issues opened by other contributors until the issue has been marked with the `help wanted` label. The Docs team needs time to assess the issue and determine the scope of the work.
+
+          For more information, see [Working on other contributors' issues](https://docs.github.com/en/contributing/collaborating-on-github-docs/about-contributing-to-github-docs#working-on-other-contributors-issues).
+          EOF

content/admin/configuring-settings/configuring-github-connect/enabling-dependabot-for-your-enterprise.md

@@ -90,7 +90,7 @@ Before you can enable {% data variables.product.prodname_dependabot_alerts %}, y
     > [!TIP]
    > We recommend configuring {% data variables.product.prodname_dependabot_alerts %} without notifications for the first few days to avoid an overload of realtime notifications. After a few days, you can enable notifications to receive {% data variables.product.prodname_dependabot_alerts %} as usual.
 
-You can now enable {% data variables.product.prodname_dependabot_alerts %} for all existing or new private and internal repositories in the enterprise settings page for "{% data variables.product.UI_advanced_security_ent %}." Alternatively, repository administrators and organization owners can enable {% data variables.product.prodname_dependabot_alerts %} for each repository and organization. Public repositories are always enabled by default. For more information, see [AUTOTITLE](/enterprise-server@latest/code-security/how-tos/secure-your-supply-chain/secure-your-dependencies/configure-dependabot-alerts).
+You can now enable {% data variables.product.prodname_dependabot_alerts %} for all existing or new private and internal repositories in the enterprise settings page for "{% data variables.product.UI_advanced_security_ent %}." Alternatively, repository administrators and organization owners can enable {% data variables.product.prodname_dependabot_alerts %} for each repository and organization. For public repositories, {% data variables.product.prodname_dependabot_alerts %} are enabled automatically once the dependency graph is enabled for the repository. For more information, see [AUTOTITLE](/enterprise-server@latest/code-security/how-tos/secure-your-supply-chain/secure-your-dependencies/configure-dependabot-alerts).
 
 ## Enabling {% data variables.product.prodname_dependabot_updates %}
 

content/authentication/keeping-your-account-and-data-secure/about-anonymized-urls.md

@@ -19,6 +19,14 @@ Videos also get anonymized URLs with the same format as image URLs, but are not
 
 Anyone who receives your anonymized URL, directly or indirectly, may view your image or video. To keep sensitive media files private, restrict them to a private network or a server that requires authentication instead of using Camo.
 
+## Removing {% data variables.product.github %}-hosted attachments
+
+Files and images hosted under `github.com/user-attachments/` are separate from the comments and pull request descriptions that link to them. Removing a link from an issue comment or pull request description does not necessarily delete the uploaded file. An image uploaded while editing a pull request description can remain available even if you remove it before saving the description.
+
+To ask about removing an uploaded attachment, contact {% data variables.contact.contact_support %}. Support may be able to help remove it even if you no longer have its original URL. After an attachment is deleted, its URL should return a 404 error.
+
+Attachment deletion is different from purging an image from Camo's cache. For more information about purging the cache, see [Removing an image from Camo's cache](#removing-an-image-from-camos-cache).
+
 ## Troubleshooting issues with Camo
 
 In rare circumstances, images that are processed through Camo might not appear on {% data variables.product.prodname_dotcom %}. Here are some steps you can take to determine where the problem lies.

content/billing/how-tos/products/use-cost-centers.md

@@ -49,6 +49,14 @@ After you create a cost center, you can add a monthly budget and receive alerts
 
 You can view the usage of your cost centers and download the usage data for further analysis. See [AUTOTITLE](/billing/tutorials/gather-insights).
 
+## Finding the cost center for a resource
+
+You can use the REST API to find which cost center a user, organization, repository, or enterprise team belongs to, without listing and searching through all cost centers.
+
+Enterprise owners and billing managers can look up any resource in the enterprise. Organization owners and holders of a custom role with fine-grained read access to enterprise billing are limited to resources and cost centers they can access.
+
+The endpoint returns the cost center's ID and name, or an empty `memberships` array if the resource is not assigned to a cost center. For parameters and authentication requirements, see [AUTOTITLE](/rest/billing/cost-centers).
+
 ## Viewing, editing, and deleting cost centers
 
 You can view, edit, and delete cost centers to manage your business units effectively.

content/billing/tutorials/control-costs-at-scale.md

@@ -242,6 +242,47 @@ The response confirms the successful addition of resources. If any resources wer
 
 If the endpoint responds with `Problems parsing JSON`, use a JSON validator to check that the data specified in the `--input` option is valid.
 
+### Verify a resource's cost center assignment
+
+After adding resources, you can look up a resource directly to check which cost center it belongs to. You don't need to list and search through all cost centers.
+
+In your terminal, run the following command, replacing `ENTERPRISE` with your enterprise slug and `USERNAME` with the login of a user you added.
+
+```shell copy
+gh api \
+  --method GET \
+  -H "Accept: application/vnd.github+json" \
+  -H "X-GitHub-Api-Version: {{ defaultRestApiVersion }}" \
+  /enterprises/ENTERPRISE/settings/billing/cost-centers/memberships \
+  -f resource_type=user \
+  -f name=USERNAME
+```
+
+The response includes the cost center's ID and name. For example, a lookup for `monalisa` assigned to the cost center created earlier returns:
+
+```json
+{
+  "resource": {
+    "type": "user",
+    "identifier": {
+      "login": "monalisa"
+    }
+  },
+  "memberships": [
+    {
+      "cost_center": {
+        "id": "3312fdf2-5950-4f64-913d-e734124059c9",
+        "name": "NAME"
+      }
+    }
+  ]
+}
+```
+
+If the resource is not assigned to a cost center, the `memberships` array is empty.
+
+You can also look up an organization, repository, or enterprise team. Set `resource_type` to `organization`, `repository`, or `team`, and set `name` to the organization slug, `owner/repo`, or enterprise team slug, respectively. See [AUTOTITLE](/rest/billing/cost-centers).
+
 ## 5. Set budgets with the REST API
 
 You can create budgets programmatically to apply spending controls to the cost centers you've created. This is particularly useful for managing usage-based costs like {% data variables.product.prodname_ai_credits_short %} at scale.

content/code-security/how-tos/secure-your-supply-chain/secure-your-dependencies/configure-security-updates.md

@@ -36,7 +36,7 @@ You can also enable or disable {% data variables.product.prodname_dependabot_sec
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-code-security-and-analysis %}
-1. To the right of "{% data variables.product.prodname_dependabot %} security updates," click **Enable** to enable the feature or **Disable** to disable it. {% ifversion fpt or ghec %}For public repositories, the button is disabled if the feature is always enabled.{% endif %}
+1. To the right of "{% data variables.product.prodname_dependabot %} security updates," click **Enable** to enable the feature or **Disable** to disable it.
 
 ## Grouping {% data variables.product.prodname_dependabot_security_updates %} into a single pull request
 

content/copilot/how-tos/copilot-cli/set-up-copilot-cli/add-lsp-servers.md

@@ -305,15 +305,15 @@ You can list and manage your LSP servers in an interactive CLI session using the
 
 | Slash command             | Description |
 |---------------------------|-------------|
-| `/lsp` or `/lsp show`     | Show the status of all configured LSP servers. |
+| `/lsp list` (or `/lsp show`) | Show the status of all configured LSP servers. |
 | `/lsp test SERVER-NAME`   | Test whether a server starts correctly. |
 | `/lsp reload`             | Reload LSP configurations from disk. |
 | `/lsp logs`               | Open the live LSP services panel to view server logs. |
-| `/lsp help`               | Show `/lsp` command information. |
+| `/lsp` or `/lsp help`     | Show `/lsp` command information. |
 
 ### Listing available LSP servers
 
-1. In {% data variables.copilot.copilot_cli_short %}, confirm that the LSP server you chose is available by using the `/lsp` slash command. You will see output such as:
+1. In {% data variables.copilot.copilot_cli_short %}, confirm that the LSP server you chose is available by using the `/lsp list` slash command. You will see output such as:
 
    ```text
    ● LSP Server Status:

content/copilot/how-tos/copilot-cli/use-copilot-cli/delegate-tasks-to-cca.md

@@ -32,7 +32,7 @@ For more information, see [AUTOTITLE](/copilot/how-tos/copilot-cli/use-copilot-c
 
 ## Delegate tasks to {% data variables.copilot.copilot_cloud_agent %}
 
-You can delegate a task to {% data variables.copilot.copilot_cloud_agent %} on {% data variables.product.github %} by using the `/delegate`slash command, followed by a prompt:
+You can delegate a task to {% data variables.copilot.copilot_cloud_agent %} on {% data variables.product.github %} by using the `/delegate` slash command, followed by a prompt:
 
 ```shell
 /delegate complete the API integration tests and fix any failing edge cases
@@ -46,6 +46,12 @@ Alternatively, prefix a prompt with `&` to delegate it:
 
 {% data variables.product.prodname_copilot_short %} will ask to commit any of your unstaged changes as a checkpoint in a new branch it creates. {% data variables.copilot.copilot_cloud_agent %} will open a draft pull request, make changes in the background, and request a review from you.
 
+By default, the pull request targets your current branch. To target a different branch, add `--base BRANCH-NAME` after `/delegate`. For example:
+
+```shell
+/delegate --base main complete the API integration tests and fix any failing edge cases
+```
+
 {% data variables.product.prodname_copilot_short %} will provide a link to the pull request and agent session on {% data variables.product.github %} once the session begins.
 
 ## Next steps

content/copilot/how-tos/copilot-cli/use-copilot-cli/manage-pull-requests.md

@@ -90,7 +90,7 @@ The `/pr` slash command has several subcommands that you can use to perform diff
 <td align="center">Yes</td>
 </tr>
 <tr>
-<td><code>/pr automerge</code></td>
+<td><code>/pr agentmerge</code></td>
 <td>Do the same as <code>/pr auto</code>, then merge the pull request once it is green. <a href="#automatically-merging-the-pull-request">Find out more</a></td>
 <td align="center">No</td>
 <td align="center">Yes</td>
@@ -224,12 +224,12 @@ You can append instructions to guide the pull request creation. For example:
 `/pr auto` deliberately stops when the pull request is green. If you also want {% data variables.product.prodname_copilot_short %} to merge the pull request, enter:
 
 ```copilot copy
-/pr automerge
+/pr agentmerge
 ```
 
 This runs the same loop as `/pr auto`. Once the pull request is no longer a draft, has no unresolved requests for changes, and all required checks are passing, {% data variables.product.prodname_copilot_short %} enables auto-merge rather than merging the pull request itself. {% data variables.product.prodname_dotcom %} then completes the merge as soon as every remaining requirement is satisfied, including any required approvals and merge queue. {% data variables.product.prodname_copilot_short %} keeps the loop running—handling any further review feedback or check failures—until the pull request is merged or closed.
 
-You can use `/pr agentmerge` as an alias for `/pr automerge`.
+You can use `/pr automerge` as an alias for `/pr agentmerge`.
 
 ## Further reading