Repo sync

content/actions/reference/workflows-and-actions/events-that-trigger-workflows.md

@@ -56,6 +56,9 @@ on:
 
 {% data reusables.actions.branch-requirement %}
 
+> [!NOTE]
+> To prevent recursive workflows, this event does not trigger workflows if the check run's check suite was created by {% data variables.product.prodname_actions %} or if the check suite's head SHA is associated with {% data variables.product.prodname_actions %}.
+
 Runs your workflow when activity related to a check run occurs. A check run is an individual test that is part of a check suite. For information, see [AUTOTITLE](/rest/guides/using-the-rest-api-to-interact-with-checks). For information about the check run APIs, see [AUTOTITLE](/graphql/reference/objects#checkrun) in the GraphQL API documentation or [AUTOTITLE](/rest/checks/runs).
 
 For example, you can run a workflow when a check run has been `rerequested` or `completed`.
@@ -78,7 +81,7 @@ on:
 {% data reusables.actions.branch-requirement %}
 
 > [!NOTE]
-> To prevent recursive workflows, this event does not trigger workflows if the check suite was created by {% data variables.product.prodname_actions %}.
+> To prevent recursive workflows, this event does not trigger workflows if the check suite was created by {% data variables.product.prodname_actions %} or if the check suite's head SHA is associated with {% data variables.product.prodname_actions %}.
 
 Runs your workflow when check suite activity occurs. A check suite is a collection of the check runs created for a specific commit. Check suites summarize the status and conclusion of the check runs that are in the suite. For information, see [AUTOTITLE](/rest/guides/using-the-rest-api-to-interact-with-checks). For information about the check suite APIs, see [AUTOTITLE](/graphql/reference/objects#checksuite) in the GraphQL API documentation or [AUTOTITLE](/rest/checks/suites).
 

content/billing/concepts/product-billing/git-lfs.md

@@ -70,6 +70,8 @@ In this example, {% data variables.product.company_short %} would bill for 1.5 G
 
 {% data reusables.billing.default-over-quota-behavior %}
 
+{% data reusables.billing.migrated-budgets %}
+
 ## Further reading
 
 * [AUTOTITLE](/repositories/working-with-files/managing-large-files/about-git-large-file-storage)

content/billing/concepts/product-billing/github-actions.md

@@ -162,3 +162,5 @@ Your {% data variables.product.prodname_actions %} usage shares your account's e
 ## Managing your budget for {% data variables.product.prodname_actions %}
 
 {% data reusables.billing.default-over-quota-behavior %}
+
+{% data reusables.billing.migrated-budgets %}

content/billing/concepts/product-billing/github-codespaces.md

@@ -81,7 +81,7 @@ You can view details of your usage for the current month at any time. See [AUTOT
 
 If you are blocked from resuming a codespace and you want to continue to work on changes you have made in your codespace, you can do any of the following:
 
-* Add a payment method and set a budget greater than $0 USD.
+* Add a payment method and review your budget settings to ensure they meet your usage needs. See [AUTOTITLE](/billing/tutorials/set-up-budgets#viewing-budgets).
 * Export the changes from the codespace to a branch. See [AUTOTITLE](/codespaces/troubleshooting/exporting-changes-to-a-branch).
 * Wait for your monthly included usage to reset at the start of the next monthly billing cycle.
 
@@ -204,6 +204,8 @@ Use of codespaces created using prebuilds is charged at the same rate as regular
 
 {% data reusables.billing.default-over-quota-behavior %}
 
+{% data reusables.billing.migrated-budgets %}
+
 {% data reusables.codespaces.exporting-changes %}
 
 ## Viewing projected usage for an organization

content/billing/concepts/product-billing/github-models.md

@@ -65,7 +65,9 @@ For accounts that use a custom model with a third-party model provider, billing
 
 Enterprises and organizations can opt in to paid usage to access expanded model capabilities, including increased request allowances and larger context windows. You can manage their spending by setting a budget.
 
-By default, organizations and personal accounts that opt in to paid usage have a spending limit of $0 US dollars (USD) until the budget is increased.
+Organizations and personal accounts may have default budgets to limit spending. Check the budgets for your account to ensure they are appropriate for your usage needs. See [AUTOTITLE](/billing/tutorials/set-up-budgets#viewing-budgets).
+
+{% data reusables.billing.migrated-budgets %}
 
 For more information, see [AUTOTITLE](/billing/managing-your-billing/using-budgets-control-spending).
 
@@ -105,24 +107,24 @@ The following table displays how the total cost is calculated for a request usin
 
 The following steps demonstrate how the total cost is calculated:
 
-1. **Calculate input tokens:**  
-    Multiply the number of input tokens by the input multiplier.  
+1. **Calculate input tokens:**
+    Multiply the number of input tokens by the input multiplier.
     `1,000,000 tokens × 0.25 = 250,000 input token units`
 
-1. **Calculate billable output tokens:**  
-    Multiply the number of output tokens by the output multiplier.  
+1. **Calculate billable output tokens:**
+    Multiply the number of output tokens by the output multiplier.
     `1,000,000 tokens × 1 = 1,000,000 output token units`
 
-1. **Add billable tokens:**  
-    Add the billable input and output tokens.  
+1. **Add billable tokens:**
+    Add the billable input and output tokens.
     `250,000 (input) + 1,000,000 (output) = 1,250,000 total token units`
 
-1. **Charges by type:**  
-   * **Input charge:** `250,000 × $0.00001 = $2.50`  
+1. **Charges by type:**
+   * **Input charge:** `250,000 × $0.00001 = $2.50`
    * **Output charge:** `1,000,000 × $0.00001 = $10.00`
 
-1. **Calculate the total cost:**  
-    Multiply the total token units by the token unit price.  
+1. **Calculate the total cost:**
+    Multiply the total token units by the token unit price.
     `1,250,000 × $0.00001 = $12.50 for this request`
 
 ## Opting out of paid usage

content/billing/concepts/product-billing/github-packages.md

@@ -91,3 +91,5 @@ Your {% data variables.product.prodname_registry %} usage shares your account's
 ## Managing your budget for {% data variables.product.prodname_registry %}
 
 {% data reusables.billing.default-over-quota-behavior %}
+
+{% data reusables.billing.migrated-budgets %}

content/billing/tutorials/set-up-budgets.md

@@ -34,9 +34,9 @@ Budgets and alerts allow you to track spending on metered products for your acco
 
 If your account does not have a valid payment method on file, usage is blocked once you use up your quota.
 
-By default, if you have a valid payment method on file, spending is limited to $0 USD until you set a budget. You can set and manage a budget to limit spending for a product or SKU.
+If you have a valid payment method on file, spending may be limited by one or more budgets. Check the budgets set for your account to ensure they are appropriate for your usage needs.
 
-<!--Billing: default budget-->
+{% data reusables.billing.migrated-budgets %}
 
 ## About budgets
 
@@ -126,7 +126,7 @@ As the owner of an enterprise or organization account, or as a billing manager,
 
 ### Editing or deleting a budget
 
->[!IMPORTANT] Deleting a budget may remove any limits on spending, depending on your other existing budgets. For example, deleting the default $0 budget for {% data variables.product.prodname_copilot_short %} premium requests allows for unlimited usage.
+>[!IMPORTANT] Deleting a budget may remove any limits on spending, depending on your other existing budgets. For example, deleting the only budget that limits {% data variables.product.prodname_copilot_short %} premium requests allows for unlimited usage.
 
 You can edit or delete a budget at any time, but you cannot change the scope of a budget after creating it.
 

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

@@ -13,6 +13,7 @@ topics:
   - Secret Protection
   - Repositories
 children:
+  - /remediating-a-leaked-secret
   - /push-protection-for-users
   - /working-with-push-protection-from-the-command-line
   - /working-with-push-protection-from-the-rest-api