Merge pull request #43933 from github/repo-sync

Repo sync

Author: docs-bot

.github/workflows/index-general-search-pr.yml

@@ -64,7 +64,7 @@ jobs:
 
           # first sleep to give it a chance to start
           sleep 6
-          curl --retry-connrefused --retry 4 -I http://localhost:4002/
+          curl --retry-connrefused --retry 6 -I http://localhost:4002/
 
       - if: ${{ failure() }}
         name: Debug server outputs on errors

content/billing/how-tos/set-up-payment/manage-payment-info.md

@@ -1,6 +1,6 @@
 ---
 title: Managing your payment and billing information
-intro: 'Learn how to view and manage your payment information and billing contacts using the new billing platform.'
+intro: 'Learn how to view, modify, and remove your payment information and billing contacts using the new billing platform.'
 versions:
   feature: enhanced-billing-platform
 redirect_from:

content/code-security/reference/supply-chain-security/dependabot-options-reference.md

@@ -573,7 +573,7 @@ Package manager | YAML value      | Supported versions |
 | pip-compile | `pip`            | 7.5.3            |
 | pipenv      | `pip`            | <= 2024.4.1      |
 | pnpm   | `npm`            | v7, v8 <br>v9, v10 (version updates only)    |
-| poetry      | `pip`    | 2.2.1    |
+| poetry      | `pip`    | v2    |
 | {% ifversion dependabot-pre-commit-support %} |
 | pre-commit | `pre-commit` | Not applicable |
 | {% endif %} |

content/copilot/how-tos/use-copilot-agents/cloud-agent/integrate-cloud-agent-with-jira.md

@@ -18,7 +18,7 @@ category:
 > * {% data variables.product.prodname_copilot %} uses AI. Check for mistakes. See [AUTOTITLE](/copilot/responsible-use/copilot-cloud-agent).
 > * You can provide feedback about the {% data variables.product.prodname_copilot %} for Jira integration in the [{% data variables.product.github %} survey](https://www.surveymonkey.com/r/CCAforJira).
 
-The {% data variables.product.prodname_copilot %} integration in Jira allows you to invoke {% data variables.copilot.copilot_cloud_agent %} without leaving your Jira workspace. From within a Jira work item you can initiate {% data variables.copilot.copilot_cloud_agent_short %} sessions and open pull requests, using the context of the work item's title, description, labels, and comments.
+The {% data variables.product.prodname_copilot %} integration in Jira allows you to invoke {% data variables.copilot.copilot_cloud_agent %} without leaving your Jira workspace. From within a Jira work item you can initiate {% data variables.copilot.copilot_cloud_agent_short %} sessions and open pull requests, using the context of the work item's title, description, labels, comments, and any Atlassian custom fields such as acceptance criteria.
 
 ## Prerequisites
 
@@ -71,7 +71,7 @@ Once the {% data variables.product.prodname_copilot %} for Jira app has been ins
 
 To enable the {% data variables.product.prodname_copilot %} for Jira app for an organization:
 
-1. In Jira, go to the settings page for your space.
+1. In Jira, go to the settings page for your workspace.
 1. Go to the applications setting page for the {% data variables.product.prodname_copilot %} app.
 1. Optionally, click **Connect More {% data variables.product.github %} Organizations** to add new organizations to the list.
 1. Enable the {% data variables.product.prodname_copilot_short %} app for one or more of the listed organizations.
@@ -90,8 +90,6 @@ You can trigger {% data variables.copilot.copilot_cloud_agent %} in three ways:
 * **Mention** `@{% data variables.product.prodname_copilot %}` in a comment on a work item.
 * **Add {% data variables.product.prodname_copilot_short %} to a workflow transition** so it is triggered automatically when a work item moves to a specific status. See [Collaborate on work items with AI agents](https://support.atlassian.com/jira-software-cloud/docs/collaborate-on-work-items-with-ai-agents/#Add-an-agent-to-workflow-transitions) for setup instructions.
 
-To change the model used by {% data variables.copilot.copilot_cloud_agent %} for a specific task, include the model name in your instructions to {% data variables.product.prodname_copilot_short %}. For example, you can say `@{% data variables.product.prodname_copilot %} use Claude Sonnet 4.5 to create a new API endpoint for user authentication in octo-org/octorepo`. If you do not specify a model, {% data variables.copilot.copilot_cloud_agent %} will use the default model for coding tasks, see [AUTOTITLE](/copilot/how-tos/use-copilot-agents/cloud-agent/changing-the-ai-model).
-
 > [!NOTE]
 > When you assign {% data variables.product.prodname_copilot_short %} to a Jira work item, the context the agent captures from Jira will be added to the pull request and **visible to everyone** if the repository is public.
 
@@ -114,6 +112,26 @@ To change the model used by {% data variables.copilot.copilot_cloud_agent %} for
 > [!TIP]
 > If you have not received confirmation of triggering {% data variables.copilot.copilot_cloud_agent %} after 1 minute, refresh the Jira work item page.
 
+## Customizing {% data variables.copilot.copilot_cloud_agent %} in Jira
+
+You can customize how {% data variables.copilot.copilot_cloud_agent %} works in your Jira workspace by specifying models, agents, custom instructions, and branching rules.
+
+### Specifying a model
+
+To change the model used by {% data variables.copilot.copilot_cloud_agent %} for a specific task, include the model name in your instructions to {% data variables.product.prodname_copilot_short %}. For example, you can say `@{% data variables.product.prodname_copilot %} use Claude Sonnet 4.5`. If you do not specify a model, {% data variables.copilot.copilot_cloud_agent %} will use the default model for coding tasks, see [AUTOTITLE](/copilot/how-tos/use-copilot-agents/cloud-agent/changing-the-ai-model).
+
+### Specifying a custom branch
+
+{% data variables.copilot.copilot_cloud_agent_short_cap_c %} respects branch naming rules specified in individual Atlassian tickets. If a ticket includes specific branching conventions, {% data variables.product.prodname_copilot_short %} will read and follow them when creating pull requests, keeping your repository consistent with your existing workflow.
+
+### Specifying a custom agent
+
+You can specify a custom agent from your {% data variables.product.github %} repository directly in the Jira ticket. This allows teams to tailor {% data variables.copilot.copilot_cloud_agent_short %}'s behavior to their specific needs. For more information, see [AUTOTITLE](/copilot/how-tos/use-copilot-agents/cloud-agent/create-custom-agents).
+
+### Using custom instructions
+
+You can define custom instructions at the Jira workspace level that apply every time {% data variables.copilot.copilot_cloud_agent %} is triggered. Use these instructions to specify defaults such as the target repository, default branch naming rules, preferred models, or particular agents to use. This reduces repetitive configuration and increases control over the agent's behavior.
+
 ## Usage costs
 
 {% data variables.copilot.copilot_cloud_agent %} uses {% data variables.product.prodname_actions %} minutes and {% data variables.product.prodname_copilot_short %} premium requests.

content/migrations/ado/index.md

@@ -20,7 +20,7 @@ redirect_from:
 introLinks:
   ado_key_differences: /migrations/ado/key-differences-between-azure-devops-and-github
 contentType: tutorials
-heroImage: /assets/images/banner-images/hero-3
+heroImage: /assets/images/banner-images/hero-2
 sidebarLink:
   text: Get started
   href: /migrations/ado

data/features/dependabot-poetry-pep621.yml

@@ -0,0 +1,5 @@
+# Poetry PEP 621 project section support for Dependabot
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '> 3.21'

data/release-notes/enterprise-server/3-18/8.yml

@@ -71,6 +71,8 @@ sections:
     - |
       To improve page load performance, user profile pages display a maximum of 24 organizations. When viewing your own profile, a "View all" link provides access to the full list in organization settings. When viewing another user's profile, a count displays any additional organizations beyond the first 24.
   known_issues:
+    - |
+      On instances configured for high availability, you will not be able to change GitHub Actions settings through the Management Console. Other settings are not affected. [Updated: 2026-04-22]
     - |
       First time setups of GitHub Actions with OpenID Connect (OIDC) fail with an error on the `Update Servicing Resources` step. This problem does not affect instances where GitHub Actions is already enabled.
 

data/release-notes/enterprise-server/3-19/5.yml

@@ -83,6 +83,8 @@ sections:
     - |
       To improve page load performance, user profile pages display a maximum of 24 organizations. When viewing your own profile, a "View all" link provides access to the full list in organization settings. When viewing another user's profile, a count displays any additional organizations beyond the first 24.
   known_issues:
+    - |
+      On instances configured for high availability, you will not be able to change GitHub Actions settings through the Management Console. Other settings are not affected. [Updated: 2026-04-22]
     - |
       First time setups of GitHub Actions with OpenID Connect (OIDC) fail with an error on the `Update Servicing Resources` step. This problem does not affect instances where GitHub Actions is already enabled.
 

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

@@ -83,6 +83,8 @@ sections:
     - |
       To improve page load performance, user profile pages display a maximum of 24 organizations. When viewing your own profile, a "View all" link provides access to the full list in organization settings. When viewing another users profile, a count displays any additional organizations beyond the first 24.
   known_issues:
+    - |
+      On instances configured for high availability, you will not be able to change GitHub Actions settings through the Management Console. Other settings are not affected. [Updated: 2026-04-22]
     - |
       First time setups of GitHub Actions with OpenID Connect (OIDC) fail with an error on the `Update Servicing Resources` step. This problem does not affect instances where GitHub Actions is already enabled.
 
@@ -120,4 +122,4 @@ 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.
     - |
-      In GHES instances that have multiple git storage nodes in a voting configurations (That includes GHES Clusters and Geo Replicate HA instances) where Actions is enabled can encounter problem a upon upgrading.  The 1st part actions that are shipped with the new version of GHES can not be correctly installed.  This can block upgrade and in some cases leave the old versions of these actions within the instatance.
+      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`.

data/reusables/billing/manage-payment-info.md

@@ -8,9 +8,13 @@
 
 1. From the list of "Billing & licensing" pages, click **Payment information** to display full details of your payment method.
 
-1. To edit your payment method:
+1. To edit or remove your payment method:
 
-   * **Bank card or PayPal**: In "Payment method", click **Edit** to update your payment information.
+   * **Bank card or PayPal**: In "Payment method", click **Edit** to update your payment information or click **Remove** to remove your payment information.
    * **Azure subscription**: Under "Azure subscription", click {% octicon "pencil" aria-label="Edit Azure Subscription" %} to edit your subscription or {% octicon "trash" aria-label="Delete Azure Subscription" %} to remove your subscription. See [AUTOTITLE](/billing/how-tos/set-up-payment/connect-azure-sub).
 
->[!NOTE] You may see an authorization hold on your provided payment method once it's updated or after accruing significant usage of metered services. Authorization holds are temporary and are released as quickly as possible.
+>[!NOTE]
+> * You may see an authorization hold on your provided payment method once it's updated or after accruing significant usage of metered services. Authorization holds are temporary and are released as quickly as possible.
+> * If you have a paid subscription and remove your payment method, your subscription will automatically cancel on your next renewal date.
+> * If you are currently on an active paid trial, you will not be able to remove your payment method.
+> * To remove a payment method, you must have a balance of zero, and no billable metered usage in the current month, or the previous month if has yet to be paid.