Repo sync

.github/workflows/check-for-spammy-prs.yml

@@ -39,9 +39,10 @@ jobs:
             const touchesTooMany = files.length > 10
             const totalChanges = files.reduce((sum, f) => sum + f.additions + f.deletions, 0)
             const isOneLineAddition = files.every(f => f.status === 'added') && totalChanges <= 1
+            const isBlankLineEdit = totalChanges <= 1 && files.every(f => f.status === 'modified')
 
             // Close the PR and add the invalid label
-            if (onlyDeletes || isEmptyCommit || touchesTooMany || isOneLineAddition) {
+            if (onlyDeletes || isEmptyCommit || touchesTooMany || isOneLineAddition || isBlankLineEdit) {
               await github.rest.issues.update({
                 owner: owner,
                 repo: repo,

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

@@ -54,4 +54,4 @@ jobs:
           FILE_PATHS_NOT_ALLOWED: ${{ steps.filter.outputs.notAllowed_files }}
           CHANGED_FILE_PATHS: ${{ steps.filter.outputs.contentTypes_files }}
           ADDED_CONTENT_FILES: ${{ steps.filter.outputs.added_files }}
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: ${{ secrets.DOCS_BOT_PAT_BASE }}

content/actions/how-tos/troubleshoot-workflows.md

@@ -97,7 +97,7 @@ Specific events allow for filtering by branch, tag, and/or paths you can customi
 
 You can use special characters with filters. For more information, see [AUTOTITLE](/actions/reference/workflows-and-actions/workflow-syntax#filter-pattern-cheat-sheet).
 
-For path filtering, evaluating diffs is limited to the first 300 files. If there are files changed that are not matched in the first 300 files returned by the filter, the workflow will not be run. For more information, see [AUTOTITLE](/actions/reference/workflows-and-actions/workflow-syntax#git-diff-comparisons).
+For path filtering, evaluating diffs is limited to the first {% ifversion actions-paths-filter-limit %}3,000{% else %}300{% endif %} files. If there are files changed that are not matched in the first {% ifversion actions-paths-filter-limit %}3,000{% else %}300{% endif %} files returned by the filter, the workflow will not be run. For more information, see [AUTOTITLE](/actions/reference/workflows-and-actions/workflow-syntax#git-diff-comparisons).
 
 ## Troubleshoot workflow execution
 

content/billing/concepts/budgets-and-alerts.md

@@ -28,7 +28,7 @@ Each budget has a type and a scope that define which paid use contributes to spe
 
   * **Universal**: applies to all licensed users by default
   * **Cost center user-level**: applies to every user in a cost center
-  * **Individual**: overrides the above for specific users
+  * **Individual**: overrides the above for specific users, and can be given an optional expiration date so a temporary override is removed automatically
 
 For {% data variables.product.prodname_copilot_short %}, cost centers can also have included usage controls, which cap how much of the shared {% data variables.product.prodname_ai_credits_short %} pool a cost center can use before metered usage begins. This is a separate control from the budgets and the included usage alerts described below. See [AUTOTITLE](/copilot/concepts/billing/budgets-for-usage-based-billing#included-usage-controls-for-cost-centers).
 

content/billing/how-tos/set-up-budgets.md

@@ -120,6 +120,14 @@ As the owner of an enterprise or organization account, or as a billing manager,
      * Select a cost center to create a user-level budget that applies to every user in that cost center. This sets one per-user amount for all current and future members, and overrides the universal budget for them.
      * Select a specific user to create an individual budget that overrides both the universal budget and any cost center user-level budget for that user.
 
+1. If you selected a specific user, optionally set an expiration date for the individual budget under "Expiration".
+
+   * **No expiration**: The budget applies until you edit or delete it. This is the default.
+   * **End of current billing cycle**: {% data variables.product.github %} removes the budget when the current billing cycle ends.
+   * **Specific date**: {% data variables.product.github %} removes the budget on the date you choose.
+
+   When an individual budget expires, {% data variables.product.github %} removes it and the user falls back to the next budget that applies to them: their cost center user-level budget, if they have one, or otherwise the universal user-level budget. If neither budget is configured, no user-level budget applies. See [AUTOTITLE](/copilot/concepts/billing/budgets-for-usage-based-billing#expiration-dates-for-individual-user-level-budgets).
+
 1. Under "Budget", set a budget amount or license count.
 
    To stop any usage and further spending once the budget limit is reached, select **Stop usage when budget limit is reached** or **Limit usage when budget limit is reached**, if available. **This option is available for metered products and for {% data variables.product.prodname_AS %} SKU-level budgets**. For {% data variables.product.prodname_AS %}, this option prevents new enablement on additional repositories. It doesn't disable {% data variables.product.prodname_AS %} on repositories where it is already active. See [AUTOTITLE](/billing/concepts/product-billing/github-advanced-security#hard-budgets-for-github-advanced-security-skus).
@@ -145,6 +153,8 @@ As the owner of an enterprise or organization account, or as a billing manager,
 
 You can edit or delete a budget at any time, but you cannot change the scope of a budget after creating it.
 
+For an individual user-level budget, you can also change or clear the expiration date at any time.
+
 1. Navigate to the "Budgets and alerts" view. See [Viewing budgets](#viewing-budgets).
 1. In the list of budgets, click {% octicon "kebab-horizontal" aria-label="View actions" %} next to the budget you want to edit, and click **{% octicon "pencil" aria-hidden="true" aria-label="pencil" %} Edit** or **{% octicon "trash" aria-hidden="true" aria-label="trash" %} Delete**.
 1. Follow the prompts.