Repo sync

Dockerfile

@@ -10,7 +10,7 @@
 # ---------------------------------------------------------------
 # To update the sha:
 # https://github.com/github/gh-base-image/pkgs/container/gh-base-image%2Fgh-base-noble
-FROM ghcr.io/github/gh-base-image/gh-base-noble:20260903-185405-g03e243e8e@sha256:d7ed0adc25b453b64b7ba7bfb9c81b786063d9d18d0161a81effbba2ba109873 AS base
+FROM ghcr.io/github/gh-base-image/gh-base-noble:20260914-014148-gb620b63bf@sha256:fe199dcd96e01f53c42d077dee87f428e8341379aab0987721e16b32462feb05 AS base
 
 # Install curl for Node install and determining the early access branch
 # Install git for cloning docs-early-access & translations repos

content/actions/how-tos/manage-runners/self-hosted-runners/customize-containers.md

@@ -100,7 +100,7 @@ The `prepare_job` command is called when a job is started. {% data variables.pro
   "state": {},
   "args": {
     "jobContainer": {
-      "image": "node:18"
+      "image": "node:18",
       "workingDirectory": "/__w/octocat-test2/octocat-test2",
       "createOptions": "--cpus 1",
       "environmentVariables": {

content/actions/reference/workflows-and-actions/expressions.md

@@ -412,18 +412,18 @@ You may also use the `*` syntax on an object. For example, suppose you have an o
   "scallions":
   {
     "colors": ["green", "white", "red"],
-    "ediblePortions": ["roots", "stalks"],
+    "ediblePortions": ["roots", "stalks"]
   },
   "beets":
   {
     "colors": ["purple", "red", "gold", "white", "pink"],
-    "ediblePortions": ["roots", "stems", "leaves"],
+    "ediblePortions": ["roots", "stems", "leaves"]
   },
   "artichokes":
   {
     "colors": ["green", "purple", "red", "black"],
-    "ediblePortions": ["hearts", "stems", "leaves"],
-  },
+    "ediblePortions": ["hearts", "stems", "leaves"]
+  }
 }
 ```
 
@@ -434,7 +434,7 @@ The filter `vegetables.*.ediblePortions` could evaluate to:
 [
   ["roots", "stalks"],
   ["hearts", "stems", "leaves"],
-  ["roots", "stems", "leaves"],
+  ["roots", "stems", "leaves"]
 ]
 ```
 

content/actions/tutorials/publish-packages/publish-nodejs-packages.md

@@ -110,7 +110,7 @@ If you do provide the `repository` key in your `package.json` file, then the rep
   "repository": {
     "type": "git",
     "url": "https://github.com/octocat/my-other-repo.git"
-  },
+  }
 }
 ```
 

content/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md

@@ -146,23 +146,34 @@ You can define how long custom image versions are retained and when they become
   * **Default**: 60 days
   * **Configurable range**: 7–90 days
 
-## {% ifversion ghes %}Artifact, log, and cache settings{% else %}Artifact and log retention{% endif %}
+<!-- Anchor to maintain the existing "#artifact-and-log-retention" link from other articles. -->
+<a name="artifact-and-log-retention"></a>
+## {% ifversion ghes %}Check, workflow run, status, artifact, log, and cache settings{% else %}Check, workflow run, status, artifact and log retention{% endif %}
 
 {% ifversion ghes %}
 
-These policies control storage of artifacts, logs, and caches.
+These policies control storage of checks, workflow runs, commit statuses, artifacts, logs, and caches.
 
-### Artifact and log retention
+### Check, workflow run, status, artifact and log retention
 
 {% endif %}
 
-By default, artifacts and log files generated by workflows are retained for 90 days. {% ifversion ghes %}You can change this retention period to anywhere between 1 and 400 days.{% else %}You can change the retention period.
+By default, checks, workflow runs, commit statuses, and the artifacts and log files generated by workflows are retained for 90 days. {% ifversion ghes %}You can change this retention period to anywhere between 1 and 400 days.{% else %}You can change the retention period.
 
 * For public repositories, you can configure a period between 1 and 90 days.
 * For private and internal repositories, you can configure a period between 1 and 400 days.
 {% endif %}
 
-Changes only apply to new artifacts and log files.
+{% ifversion ghec %}
+
+> [!IMPORTANT]
+> Starting October 1, 2026, these policies will apply to checks, workflow runs, and commit statuses in addition to artifacts and logs. Until then, checks, workflow runs, and commit statuses are retained for 400+ days regardless of your configured retention period. Make sure to review your retention setting and make any adjustments before October 1. For more information, see [the {% data variables.product.company_short %} changelog](https://github.blog/changelog/2026-07-17-actions-retention-will-cover-checks-workflow-runs-and-statuses/).
+
+{% endif %}
+
+{% data reusables.actions.checks-and-statuses-retention-scope %}
+
+Changes only apply to new checks, workflow runs, commit statuses, artifacts, and log files.
 
 {% ifversion ghec %}
 

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

@@ -159,6 +159,10 @@ For an individual user-level budget, you can also change or clear the expiration
 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.
 
+### Managing requests for additional budget
+
+When a member exhausts a {% data variables.product.prodname_copilot_short %} {% data variables.product.prodname_ai_credits_short %} budget, they can ask you to increase it. See [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-budget-requests).
+
 ### Controlling included usage for a cost center
 
 Budgets cap metered charges after the shared pool of {% data variables.product.prodname_ai_credits_short %} is exhausted. To cap how much of the pool a cost center can use **before** the metered phase, use an included usage control. {% data variables.product.github %} sets the cap automatically based on the licenses assigned to the cost center, and you choose whether members are blocked or roll into paid overage when the cap is reached. See [AUTOTITLE](/copilot/concepts/billing-and-usage/organizations-and-enterprises/budgets#included-usage-controls-for-cost-centers) and [AUTOTITLE](/billing/concepts/cost-centers).

content/billing/reference/billing-roles.md

@@ -39,6 +39,7 @@ You have full administrative access to your organization. You can:
 
 * View metered usage and budgets for your organization and its repositories.
 * Set budgets for the organization and its repositories.
+* Review requests from members for additional {% data variables.product.prodname_copilot_short %} budget.
 * Download CSV usage reports.
 * View promotions and discounts.
 * View spending for pre-purchased user licenses for {% data variables.product.prodname_AS %} based on your usage.
@@ -57,6 +58,7 @@ You can:
 * See enterprise usage, including costs for organizations and repositories.
 * Download CSV usage reports for products your enterprise is using.
 * Set budgets for your enterprise.
+* Review requests from members for additional {% data variables.product.prodname_copilot_short %} budget.
 * Create cost centers for all organizations within your enterprise.
 * View and manage user licenses.
 * Manage other billing settings, such as payment methods and billing contacts.

content/copilot/concepts/agents/hooks.md

@@ -62,7 +62,7 @@ You configure hooks using a special JSON format. The JSON must contain a `versio
         "env": { "KEY": "value" },
         "timeoutSec": 30
       }
-    ],
+    ]
   }
 }
 ```

content/copilot/concepts/billing-and-usage/individuals/billing.md

@@ -88,6 +88,9 @@ For guidance on how to optimize your usage and reduce spend, including how to se
 
 ## What happens if I exceed my included {% data variables.product.prodname_ai_credits_short %}?
 
+> [!NOTE]
+> This section applies to users who are on a {% data variables.copilot.copilot_individuals_short %} plan. {% data reusables.copilot.request-ai-credit-allocation-increase %}
+
 When your {% data variables.product.prodname_ai_credits_short %} are exhausted, you can:
 
 * **Upgrade your plan.** As you approach your usage limits, {% data variables.product.prodname_copilot_short %} prompts you to upgrade to the next tier. The upgrade cost is only the price difference between your current plan and the new plan, _not_ the full price of the new plan. Your usage from earlier in the billing cycle is counted within the new plan's larger allowance, so the additional credits are available to you immediately. You won't be charged for both plans for the same period.

content/copilot/concepts/billing-and-usage/organizations-and-enterprises/budgets.md

@@ -165,6 +165,7 @@ A blocked user remains blocked until one of the following happens:
 
 * The next billing cycle begins and monthly consumption resets.
 * An administrator increases the relevant budget.
+* The user requests additional budget and an administrator approves the request.
 
 ## Next steps
 

content/copilot/get-started/quickstart-copilot-app.md

@@ -51,15 +51,15 @@ In this quickstart, you will:
 
 To work on code, you need at least one project connected to the app. A project can be a folder already on your machine, including a repository you've already cloned locally, or a repository you clone from {% data variables.product.github %} or another remote Git host such as Azure DevOps. Connecting a project unlocks the core app workflow: reading code, making edits, and opening pull requests from agent sessions. If you skipped project setup during onboarding, or want to add more projects later:
 
-1. Click the **+** button in the sidebar next to "Sessions".
+1. In the sidebar, next to **Projects**, click {% octicon "plus" aria-label="Add project" %}.
 1. Under **Add project from**, choose one of the following:
   * **Local folder or repository** — Select a folder already on your machine, including one that contains a repository you've already cloned locally.
   * **{% data variables.product.github %} repository** — Browse and clone a repository from {% data variables.product.github %}.
   * **Repository URL** — Clone from a Git URL for repositories hosted outside {% data variables.product.github %} (for example, on Azure DevOps) or for private repositories without app access.
 
 ## Making your first code changes
 
-1. Click **+** next to **Sessions**, then choose a connected folder or repository under **Start session in**.
+1. Under **Projects** in the sidebar, find the connected folder or repository you want to use, then click {% octicon "plus" aria-label="Start a new session" %} next to it.
 1. Select a session mode from the dropdown below the prompt field—for example, **Interactive** to work collaboratively with the agent.
 1. In the prompt box, paste this prompt:
 
@@ -79,11 +79,12 @@ To work on code, you need at least one project connected to the app. A project c
 
 The sidebar gives you access to the main areas of the app:
 
+* **New** — Start a new agent session.
 * **[My work](https://github.com/copilot/app/launch?open=ghapp%3A%2F%2Fmywork)** — Browse and filter issues and pull requests from your repositories, check CI status, and leave reviews.
 * **[Automations](https://github.com/copilot/app/launch?open=ghapp%3A%2F%2Fautomations)** — Saved agent tasks that run on a schedule or on demand.
 * **Customize** — Discover and manage plugins, skills, MCP servers, and canvases.
 * **Search** — Search across your repositories directly from the app.
-* **Sessions** — Active agent sessions, grouped by project.
+* **Projects** — View connected projects and their active agent sessions, or start a new session for a project.
 * **Chats** — General conversations that do not require a dedicated branch or workspace.
 
 ## Next steps

content/copilot/how-tos/administer-copilot/index.md

@@ -7,6 +7,7 @@ versions:
 children:
   - /manage-for-organization
   - /manage-for-enterprise
+  - /manage-budget-requests
   - /manage-mcp-usage
   - /download-activity-report
   - /view-usage-and-adoption

content/copilot/how-tos/administer-copilot/manage-budget-requests.md

@@ -0,0 +1,23 @@
+---
+title: Managing requests for additional Copilot budget
+shortTitle: Manage budget requests
+intro: 'Approve, adjust, or deny requests from members who have used all the {% data variables.product.prodname_ai_credits_short %} in their budget.'
+permissions: 'Organization owners, enterprise owners, and billing managers'
+versions:
+  feature: enhanced-billing-platform
+contentType: how-tos
+category:
+  - Manage Copilot for a team
+---
+
+When a member uses all the {% data variables.product.prodname_ai_credits_short %} available to them, they are blocked from {% data variables.product.prodname_copilot_short %} features that consume {% data variables.product.prodname_ai_credits_short %}, and they can request an increase.
+
+Requests go to whichever account pays for the budget. Requests against an organization-owned budget are reviewed in the organization's settings, and requests against an enterprise-owned budget are reviewed in the enterprise's settings.
+
+## Reviewing requests
+
+1. Navigate to your organization or enterprise. For example, from the [Organizations](https://github.com/settings/organizations?ref_product=copilot&ref_type=engagement&ref_style=text) or [Enterprises](https://github.com/settings/enterprises?ref_product=copilot&ref_type=engagement&ref_style=text) pages on {% data variables.product.prodname_dotcom_the_website %}.
+1. In the settings for the account, click **{% octicon "bell" aria-hidden="true" aria-label="bell" %} Requests from members**, then review the pending requests for additional {% data variables.product.prodname_copilot_short %} budget.
+1. To approve requests, set a new amount for each one, select the requests, then click **Approve and increase**.
+
+Approving a request sets the member's budget to the amount you entered and restores their access to {% data variables.product.prodname_ai_credits_short %}.

content/copilot/how-tos/github-copilot-app/agent-sessions.md

@@ -17,7 +17,7 @@ category:
 
 Each session in the {% data variables.copilot.github_copilot_app %} runs in its own isolated workspace, so you can run multiple sessions in parallel and make progress on several tasks without conflicts.
 
-1. In the sidebar next to **Sessions**, click **+** to start a new session.
+1. In the sidebar, next to **Projects**, click {% octicon "plus" aria-label="Start a new session" %}.
 1. Choose a project—you can use a folder already on your machine, choose from {% data variables.product.github %}, or clone from a Git URL for repositories hosted outside {% data variables.product.github %} (for example, on Azure DevOps) or for private repositories without app access.
 1. From the dropdown under the prompt box, choose where the session should run: in a new working tree, in your local repository, or in a cloud sandbox. Cloud sandboxes for {% data variables.product.prodname_copilot_short %} (public preview) are fully isolated environments hosted by {% data variables.product.github %}.
 1. Select a session mode, model, and reasoning effort from the dropdowns below the prompt field. If you choose **Auto** for the model, the app selects the optimal model for your task based on task complexity.

content/copilot/how-tos/github-copilot-app/open-with-deep-links.md

@@ -227,7 +227,7 @@ The following app links can be wrapped in the hosted launcher. Query strings and
 
 | App link shape | Opens | Notes |
 | --- | --- | --- |
-| `ghapp://` | Home | Opens the app home route. |
+| `ghapp://` | New | Opens the **New** view to start a new session. |
 | `ghapp://chats` | Chats | Opens Chats. |
 | `ghapp://mywork` | My work | Opens issues and pull requests in My work. |
 | `ghapp://github.com/OWNER/REPO` | Repository setup | Opens or clones the repository. |

content/copilot/how-tos/manage-and-track-spending/monitor-ai-usage.md

@@ -21,6 +21,9 @@ If you access {% data variables.product.prodname_copilot_short %} through a {% d
    * If a user-level budget has been set, the card shows credits consumed out of your budget total (for example, "450 / 1,000 {% data variables.product.prodname_ai_credits_short %} used").
    * If no user-level budget applies to you, the card shows the total number of {% data variables.product.prodname_ai_credits_short %} you have consumed this cycle (for example, "100 {% data variables.product.prodname_ai_credits_short %} used").
 
+> [!NOTE]
+> {% data reusables.copilot.request-ai-credit-allocation-increase %}
+
 ## For {% data variables.copilot.copilot_individuals_short %} users
 
 If you're on a {% data variables.copilot.copilot_individuals_short %} plan, you can see your individual {% data variables.product.prodname_ai_credits_short %} consumption on the **AI usage** page, under "Billing and licensing" settings.

content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md

@@ -1,13 +1,14 @@
 ---
-title: Configuring the retention period for GitHub Actions artifacts and logs in your organization
-intro: 'You can configure the retention period for {% data variables.product.prodname_actions %} artifacts and logs in your organization.'
+title: Configuring the retention period for checks, workflow runs, commit statuses, artifacts, and logs in your organization
+intro: 'Control how long checks, workflow runs, commit statuses, artifacts, and logs are retained in your organization.'
 redirect_from:
   - /github/setting-up-and-managing-organizations-and-teams/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization
 versions:
   fpt: '*'
   ghes: '*'
   ghec: '*'
 shortTitle: Configure retention period
+allowTitleToDifferFromFilename: true
 category:
   - Configure organization features
 ---

content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md

@@ -205,15 +205,17 @@ For more information about cache eviction, see [AUTOTITLE](/actions/reference/wo
 
 {% endif %}
 
-## Configuring the retention period for {% data variables.product.prodname_actions %} artifacts and logs in your repository
+<!-- Anchor to maintain the existing "#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository" link from other articles. -->
+<a name="configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository"></a>
+## Configuring the retention period for checks, workflow runs, commit statuses, artifacts, and logs in your repository
 
-You can configure the retention period for {% data variables.product.prodname_actions %} artifacts and logs in your repository.
+You can configure the retention period for checks, workflow runs, commit statuses, artifacts, and logs in your repository.
 
 {% data reusables.actions.about-artifact-log-retention %}
 
 You can also define a custom retention period for a specific artifact created by a workflow. For more information, see [AUTOTITLE](/actions/how-tos/manage-workflow-runs/remove-workflow-artifacts#setting-the-retention-period-for-an-artifact).
 
-## Setting the Artifact and Log retention period for a repository
+## Setting the check, workflow run, status, artifact and log retention period for a repository
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}

content/rest/using-the-rest-api/github-event-types.md

@@ -89,7 +89,7 @@ Link: <https://api.github.com/resource?page=2>; rel="next",
       "gravatar_id": "",
       "url": "https://api.github.com/orgs/github",
       "avatar_url": "https://github.com/images/error/octocat_happy.gif"
-    },
+    }
   }
 ]
 ```