Repo sync

config/kubernetes/default/deployments/webapp.yaml

@@ -65,10 +65,18 @@ spec:
             preStop:
               exec:
                 command: ['sleep', '5']
-          readinessProbe:
+          startupProbe:
+            httpGet:
+              path: /healthcheck
+              port: http
             initialDelaySeconds: 5
+            periodSeconds: 5
+            failureThreshold: 12
+            timeoutSeconds: 5
+          readinessProbe:
+            timeoutSeconds: 5
+            periodSeconds: 10
+            failureThreshold: 3
             httpGet:
-              # WARNING: This should be updated to a meaningful endpoint for your application which will return a 200 once the app is fully started.
-              # See: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#define-readiness-probes
               path: /healthcheck
               port: http

config/kubernetes/production/deployments/webapp.yaml

@@ -32,13 +32,13 @@ spec:
               # Node is single-threaded but we want more CPUs
               # for OS and image resizing, and other binary executions
               # Better to increase replicas or memory than CPU
-              memory: 8.0Gi
+              memory: 16.0Gi
               # Absolute minimum to start app is 4500Mi
               # Would increase with more pages, versions, or languages supported
               # The additional memory helps during traffic surges
             limits:
               cpu: 16000m
-              memory: 8.0Gi
+              memory: 16.0Gi
           ports:
             - name: http
               containerPort: 4000
@@ -68,10 +68,18 @@ spec:
             preStop:
               exec:
                 command: ['sleep', '5']
-          readinessProbe:
+          startupProbe:
+            httpGet:
+              path: /healthcheck
+              port: http
             initialDelaySeconds: 5
+            periodSeconds: 5
+            failureThreshold: 12
+            timeoutSeconds: 5
+          readinessProbe:
+            timeoutSeconds: 5
+            periodSeconds: 10
+            failureThreshold: 3
             httpGet:
-              # WARNING: This should be updated to a meaningful endpoint for your application which will return a 200 once the app is fully started.
-              # See: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#define-readiness-probes
               path: /healthcheck
               port: http

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

@@ -9,7 +9,7 @@ redirect_from:
   - /billing/using-the-new-billing-platform/charging-business-units
   - /billing/managing-your-billing/charging-business-units
   - /billing/tutorials/use-cost-centers
-product: '{% data variables.product.prodname_ghe_cloud %}'
+permissions: 'Enterprise owners and billing managers'
 shortTitle: Use cost centers
 contentType: how-tos
 category:

content/billing/how-tos/set-up-payment/connect-azure-sub.md

@@ -13,7 +13,7 @@ versions:
   ghec: '*'
   ghes: '*'
 shortTitle: Connect Azure sub
-permissions: 'Billing managers or owners'
+permissions: 'Enterprise owners and organization owners'
 contentType: how-tos
 category:
   - Set up payment

content/billing/how-tos/set-up-payment/redeem-coupon.md

@@ -15,7 +15,7 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-product: 'Personal, organization, and enterprise account owners<br>Organization and enterprise billing managers'
+permissions: 'Personal account users, organization owners and billing managers, and enterprise owners and billing managers'
 shortTitle: Redeem coupon
 contentType: how-tos
 category:

content/billing/tutorials/automate-usage-reporting.md

@@ -9,7 +9,6 @@ versions:
   fpt: '*'
   ghec: '*'
 permissions: 'Enterprise owners, organization owners, and billing managers'
-product: '{% data reusables.billing.enhanced-billing-platform-product %}'
 contentType: tutorials
 category:
   - Track spending and control costs

content/billing/tutorials/gather-insights.md

@@ -3,18 +3,18 @@ title: Gathering insights on your spending
 intro: 'Get insights into the usage of your {% data variables.enterprise.enterprise_or_org %} members.'
 versions:
   feature: enhanced-billing-platform
+permissions: '{% data reusables.permissions.enhanced-billing-platform %}'
 redirect_from:
   - /billing/using-the-enhanced-billing-platform-for-enterprises/gathering-insights-on-your-spending
   - /billing/using-the-new-billing-platform/gathering-insights-on-your-spending
   - /billing/managing-your-billing/gathering-insights-on-your-spending
-product: '{% data reusables.billing.enhanced-billing-platform-product %}'
 shortTitle: Gather insights
 contentType: tutorials
 category:
   - Track spending and control costs
 ---
 
-The new billing platform provides you with the tools to:
+The billing platform provides you with the tools to:
 
 * **Get insights** into usage trends to understand how your resources are being used.
 * **Search and filter usage** by repository, product, or SKU, and group data accordingly.

content/copilot/how-tos/configure-custom-instructions/add-repository-instructions.md

@@ -43,14 +43,16 @@ This version of this article is for using repository custom instructions on the
 
 * **Agent instructions** are used by AI agents.
 
-  You can create one or more `AGENTS.md` files, stored anywhere within the repository. When {% data variables.product.prodname_copilot_short %} is working, the nearest `AGENTS.md` file in the directory tree will take precedence over other agent instructions files. For more information, see the [openai/agents.md repository](https://github.com/openai/agents.md).
+  {% data reusables.copilot.custom-instructions-agents %}
 
   Alternatively, you can use a single `CLAUDE.md` or `GEMINI.md` file stored in the root of the repository.
 
 ## Creating repository-wide custom instructions
 
 You can create your own custom instructions file from scratch. See [Writing your own copilot-instructions.md file](#writing-your-own-copilot-instructionsmd-file). Alternatively, you can ask {% data variables.copilot.copilot_coding_agent %} to generate one for you.
 
+You can create your own custom instructions file from scratch. See [Writing your own copilot-instructions.md file](#writing-your-own-copilot-instructionsmd-file). Alternatively, you can ask {% data variables.copilot.copilot_coding_agent %} to generate one for you.
+
 ### Asking {% data variables.copilot.copilot_coding_agent %} to generate a `copilot-instructions.md` file
 
 1. Navigate to the agents tab at [github.com/copilot/agents](https://github.com/copilot/agents?ref_product=copilot&ref_type=engagement&ref_style=text).

content/copilot/how-tos/copilot-cli/customize-copilot/add-custom-instructions.md

@@ -43,7 +43,7 @@ Instructions in the `AGENTS.md` file in the root directory, if found, are treate
 
 Instructions found in other `AGENTS.md` files are treated as additional instructions. Any primary instructions that are found are likely to have more effect on {% data variables.product.prodname_copilot_short %}'s responses than additional instructions.
 
-For more information, see the [openai/agents.md repository](https://github.com/openai/agents.md).
+For more information, see the [agentsmd/agents.md repository](https://github.com/agentsmd/agents.md).
 
 Alternatively, you can use `CLAUDE.md` and `GEMINI.md` files. These must be located at the root of the repository.
 

content/copilot/how-tos/manage-and-track-spending/manage-request-allowances.md

@@ -24,7 +24,6 @@ Premium request usage beyond the allowance is governed by two complementary cont
 * **Policy setting:** The **Premium request paid usage** policy determines whether users can surpass their included premium request allowance for each AI tool. This policy is enabled by default.
 * **Budget constraints:** If your enterprise or organization has a premium request SKU-level budget or a bundled premium requests budget, premium request usage will be blocked once the budget is fully consumed for the billing period.
 
-
 The **Premium request paid usage policy** must be enabled for any additional billing to occur. Budgets then control whether and when usage is stopped.
 
 You can increase the allowance for users by ensuring the policy is enabled, editing your budgets, or upgrading users to {% data variables.copilot.copilot_enterprise_short %}.
@@ -35,7 +34,6 @@ You can increase the allowance for users by ensuring the policy is enabled, edit
 * If a user receives licenses from multiple enterprises or standalone organizations, the user must select a billing entity to use premium requests. See [Managing premium request billing with multiple {% data variables.product.prodname_copilot_short %} licenses](/copilot/managing-copilot/monitoring-usage-and-entitlements/monitoring-your-copilot-usage-and-entitlements#managing-premium-request-billing-with-multiple-copilot-licenses).
 * For enterprises only, review which organizations are able to assign and are actively assigning {% data variables.product.prodname_copilot_short %} access to users. See [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-access/grant-access#enabling-copilot-for-organizations).
 
-
 ## Setting a policy for paid usage
 
 By default, premium requests over the allowance are enabled for organizations and enterprises. This allows for uninterrupted use of premium requests, unless you have a budget that caps spending on the Premium Request SKU.
@@ -48,6 +46,9 @@ You can set the policy for an enterprise or a standalone organization.
 
 ## Updating budgets
 
+> [!NOTE]
+> Enterprise billing managers can also edit and delete budgets.
+
 1. Ensure the "Premium request paid usage" policy is enabled. See [Setting a policy for paid usage](#setting-a-policy-for-paid-usage).
 1. Check the budgets for your enterprise or organizations, and edit or delete any budgets that "stop usage when budget limit is reached" for the Premium Request SKU. See [AUTOTITLE](/billing/managing-your-billing/using-budgets-control-spending#editing-or-deleting-a-budget).
 1. Premium request budget types:
@@ -58,7 +59,6 @@ Creating new budgets without deleting an existing budget does not override the e
 
  Enterprise-level budgets act as a failsafe for the entire enterprise, including any spending originating from within cost centers. If the enterprise budget is exhausted before the cost center budget, usage will be blocked. See [AUTOTITLE](/billing/concepts/budgets-and-alerts) for details on different scopes of budgets and stopping usage.
 
-
 ## Upgrading users to {% data variables.copilot.copilot_enterprise_short %}
 
 An enterprise owner can upgrade certain users to increase their base allowance of premium requests.

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

@@ -26,6 +26,9 @@ The {% data variables.product.prodname_copilot %} integration in Jira allows you
     * **Beta AI features** must be turned on. See [Control access to beta AI features](https://support.atlassian.com/organization-administration/docs/control-access-to-beta-ai-features/) in the Atlassian documentation.<!-- markdownlint-disable-line GHD046 -->
 * Installation and authentication must be completed for both Jira and {% data variables.product.github %}.
 
+> [!NOTE]
+> If your Jira site is on release tracks, you should contact Atlassian Support and ask for agents to be enabled in Jira before proceeding with the installation. For more information, see [What are release tracks?](https://support.atlassian.com/organization-administration/docs/what-are-release-tracks/) in the Atlassian documentation.
+
 ## Installation
 
 To install the {% data variables.product.prodname_copilot %} for Jira app and authorize it for your {% data variables.product.github %} organization or enterprise account, you need:
@@ -85,6 +88,8 @@ You can trigger {% data variables.copilot.copilot_coding_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_coding_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_coding_agent %} will use the default model for coding tasks, see [AUTOTITLE](/copilot/how-tos/use-copilot-agents/coding-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.
 
@@ -130,9 +135,13 @@ In Jira, check your Atlassian Administration settings for your organization are
 
 Check that you have connected your personal account on {% data variables.product.github %} to the {% data variables.product.prodname_copilot %} for Jira app.
 
-1. In Jira, go to the personal settings page for your user account.
+1. In Jira, go to the settings page for your personal account.
 1. Under your general settings, select the **{% data variables.product.prodname_copilot %} for Jira** app.
-1. If you are not already signed in with {% data variables.product.github %}, follow the prompts to authorize the application.
+1. If you are not already signed in with {% data variables.product.github %}, follow the prompts to sign in and authorize the application.
+
+### When chatting with {% data variables.product.prodname_copilot %}, you are prompted to sign in
+
+To sign in to {% data variables.product.prodname_copilot %} for Jira app, follow the steps above in [You can see the {% data variables.copilot.copilot_coding_agent %} but it is not possible to assign it to a Jira work item](#you-can-see-the-copilot-coding-agent-but-it-is-not-possible-to-assign-it-to-a-jira-work-item)
 
 ### {% data variables.product.prodname_copilot %} is not responding
 
@@ -144,4 +153,5 @@ Check that you have connected your personal account on {% data variables.product
 
 * [AUTOTITLE](/copilot/concepts/coding-agent/coding-agent)
 * [AUTOTITLE](/copilot/concepts/coding-agent/enable-coding-agent)
+* [AUTOTITLE](/copilot/how-tos/use-copilot-agents/coding-agent/extend-coding-agent-with-mcp#example-atlassian)
 * [Collaborate on work items with AI agents](https://support.atlassian.com/jira-software-cloud/docs/collaborate-on-work-items-with-ai-agents/) in the Atlassian documentation

content/copilot/reference/copilot-usage-metrics/copilot-usage-metrics.md

@@ -89,7 +89,7 @@ For example schemas of the data returned by the APIs, see [AUTOTITLE](/copilot/r
 | `totals_by_ide` | Breakdown of metrics by IDE used. |
 | `totals_by_feature` | Breakdown of metrics by {% data variables.product.prodname_copilot_short %} feature (e.g., inline chat, chat panel). |
 | `totals_by_language_feature` | Breakdown combining language and feature dimensions. |
-| `totals_by_model_feature` / `totals_by_language_model` | Model-specific breakdowns for chat activity (not completions). |
+| `totals_by_model_feature` / `totals_by_language_model` | Model-specific breakdowns for chat activity (not completions). When {% data variables.copilot.copilot_auto_model_selection_short %} is enabled, activity is attributed to the actual model used rather than appearing as `Auto`. |
 | `last_known_ide_version` / `last_known_plugin_version` | The most recent IDE and {% data variables.copilot.copilot_chat_short %} extension version detected for each user. |
 | `daily_active_cli_users` | Number of unique users in the enterprise or organization who used {% data variables.product.prodname_copilot_short %} via the CLI on a given day. This field is **independent** of IDE active user counts and is **not** included in IDE-based active user definitions. Omitted for enterprises or organizations with no CLI usage on that day. |
 | `totals_by_cli` | Breakdown of CLI-specific metrics for the enterprise or organization on a given day. Independent of IDE metrics—CLI usage is **not** reflected in other fields such as `totals_by_ide` or `totals_by_feature`. Omitted for enterprises or organizations with no CLI usage on that day. See [{% data variables.copilot.copilot_cli_short %} metrics fields](#copilot-cli-metrics-fields-api-only) below. |

data/reusables/copilot/custom-instructions-agents.md

@@ -1 +1 @@
-You can create one or more `AGENTS.md` files, stored anywhere within the repository. When {% data variables.product.prodname_copilot_short %} is working, the nearest `AGENTS.md` file in the directory tree will take precedence. For more information, see the [openai/agents.md repository](https://github.com/openai/agents.md).
+You can create one or more `AGENTS.md` files, stored anywhere within the repository. When {% data variables.product.prodname_copilot_short %} is working, the nearest `AGENTS.md` file in the directory tree will take precedence. For more information, see the [agentsmd/agents.md repository](https://github.com/agentsmd/agents.md).