From 00ec4baa9a5d687a1431b1362f3ec02df37d6d36 Mon Sep 17 00:00:00 2001 From: Lawrence Gripper Date: Mon, 12 Jan 2026 08:01:07 +0000 Subject: [PATCH 1/2] Recommend scheduled workflows for image generation (#59090) Co-authored-by: PJ Quirk Co-authored-by: Steve-Glass <84886334+Steve-Glass@users.noreply.github.com> Co-authored-by: Ben Ahmady <32935794+subatoi@users.noreply.github.com> --- .../how-tos/manage-runners/larger-runners/use-custom-images.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/content/actions/how-tos/manage-runners/larger-runners/use-custom-images.md b/content/actions/how-tos/manage-runners/larger-runners/use-custom-images.md index 4c76c2127654..82544a91631b 100644 --- a/content/actions/how-tos/manage-runners/larger-runners/use-custom-images.md +++ b/content/actions/how-tos/manage-runners/larger-runners/use-custom-images.md @@ -57,6 +57,9 @@ To configure a workflow for image generation: * Each job that includes the `snapshot` keyword creates a separate image. To generate only one image or image version, include all workflow steps in a single job. * Each successful run of a job that includes the `snapshot` keyword creates a new version of that image. + > [!NOTE] + > {% data variables.product.company_short %} recommends configuring image generation as a scheduled workflow on a weekly basis. This approach ensures dependencies remain up-to-date and have the latest security patches. For more information, see [AUTOTITLE](/actions/using-workflows/events-that-trigger-workflows#schedule). + It can take some time for your image to be fully generated and ready to use after the workflow completes. Provisioning time varies based on runner size and configuration, and may take several hours for larger runners. The image is generated only when the job completes successfully. This prevents new image versions from being created when a workflow fails or ends in an incomplete state. From b5975fa650665600b04e87fc516d4aeca48acf4a Mon Sep 17 00:00:00 2001 From: Greg Mondello <72952982+gmondello@users.noreply.github.com> Date: Mon, 12 Jan 2026 03:06:41 -0600 Subject: [PATCH 2/2] Revise cost center allocation for GHAS (#58847) Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com> --- .../reference/cost-center-allocation.md | 23 ++++++------------- 1 file changed, 7 insertions(+), 16 deletions(-) diff --git a/content/billing/reference/cost-center-allocation.md b/content/billing/reference/cost-center-allocation.md index 243f6e225592..9e41e955204a 100644 --- a/content/billing/reference/cost-center-allocation.md +++ b/content/billing/reference/cost-center-allocation.md @@ -29,33 +29,24 @@ This article contains reference information for how spending is assigned to cost | Git Large File Storage | The repository or organization where Git LFS is used. | | {% data variables.product.prodname_registry %} | The repository or organization that owns the package. | | {% data variables.product.prodname_prus_caps %} | The user who triggered the use of the {% data variables.product.prodname_pru %} (priority), or the organization they belong to. | -| {% data variables.product.prodname_GH_cs_and_sp %} | A user who uses a license. | +| {% data variables.product.prodname_GHAS %} | A user who uses a license (priority), or the organization that is billed for the license. | ## Details for license-based products To ensure your cost centers reflect spending as intended, it's important to understand how the cost of licenses is allocated to cost centers, and how changes are reflected in your bill. -### {% data variables.product.prodname_GH_cs_and_sp %} - -| User associated with a cost center | License usage charged | -|--|--| -| Direct assignment | To the cost center the user is assigned to | -| By organization membership only | To the enterprise | - -### {% data variables.product.prodname_enterprise %} and {% data variables.product.prodname_copilot %} - -Cost center allocation is slightly different for {% data variables.product.prodname_enterprise %} licenses and {% data variables.product.prodname_copilot %} licenses and usage. - -| User associated with a cost center | {% data variables.product.prodname_copilot_short %} license granted | License and product costs charged | +| User associated with a cost center | License granted | License and product costs charged | |--|--|--| -| Direct assignment | By any organization | To the cost center the user is assigned to | -| By organization membership only | By an organization assigned to a cost center | To the **cost center** the organization belongs to. If the organization does not belong to a cost center, to the **enterprise** | +| Direct assignment | By any organization | To the **cost center** the user is assigned to. | +| By organization membership only | By an organization assigned to a cost center | To the **cost center** the organization belongs to. If the organization does not belong to a cost center, to the **enterprise**. | Users who belong to multiple organizations in an enterprise or who receive a {% data variables.product.prodname_copilot_short %} license from multiple organizations: -* **{% data variables.product.prodname_enterprise %}** license usage is allocated to the oldest organization and charges are allocated to the cost center containing that organization. +* **{% data variables.product.prodname_enterprise %}** and **{% data variables.product.prodname_GHAS %}** license usage is allocated to the oldest organization and charges are allocated to the cost center containing that organization. * **{% data variables.product.prodname_copilot_short %}** license and product usage is allocated to one of the organizations and charges are allocated to the cost center containing that organization. +To confirm which organization is charged for a given user's license, you can request a detailed usage report. See [AUTOTITLE](/billing/reference/billing-reports#detailed-usage-report). + See [AUTOTITLE](/copilot/managing-copilot/managing-copilot-for-your-enterprise/managing-the-copilot-subscription-for-your-enterprise/about-billing-for-github-copilot-in-your-enterprise#about-seat-assignment-for-copilot-in-your-enterprise). ## Understanding cost center usage and attribution