Merge pull request github#39861 from github/repo-sync

docs-bot · web-flow · commit f09d5ce3b6a7 · 2025-08-15T05:38:06.000-07:00
Repo sync
diff --git a/content/admin/managing-your-enterprise-account/about-enterprise-accounts.md b/content/admin/managing-your-enterprise-account/about-enterprise-accounts.md
@@ -22,15 +22,15 @@ topics:
 
 ## What are enterprise accounts?
 
-<!-- expires 2025-06-30 -->
+<!-- expires 2026-01-30 -->
 
 <!-- When this expires, check with the stakeholder for release #4079 on whether or not the content is still needed -->
 
 {% ifversion ghec %}
-> [!NOTE] Currently, {% data variables.product.prodname_ghe_cloud %} customers who use a single organization are being automatically upgraded to an enterprise account at no additional cost. For details, see [AUTOTITLE](/admin/managing-your-enterprise-account/creating-an-enterprise-account#what-will-happen-after-i-upgrade-my-organization).
+> [!NOTE] {% data variables.product.prodname_ghe_cloud %} customers who use a single organization are being automatically upgraded to an enterprise account at no additional cost. For details, see [AUTOTITLE](/admin/managing-your-enterprise-account/creating-an-enterprise-account#what-will-happen-after-i-upgrade-my-organization).
 {% endif %}
 
-<!-- end expires 2025-06-30 -->
+<!-- end expires 2026-01-30 -->
 
 An enterprise account enables centralized management for **multiple organizations**.
 
diff --git a/content/admin/managing-your-enterprise-account/creating-an-enterprise-account.md b/content/admin/managing-your-enterprise-account/creating-an-enterprise-account.md
@@ -15,14 +15,14 @@ redirect_from:
   - /admin/overview/creating-an-enterprise-account
 ---
 
-<!-- expires 2025-06-30 -->
+<!-- expires 2026-01-30 -->
 
 <!-- When this expires, check with the stakeholder for release #4079 on whether or not the content is still needed -->
 <!-- If the content is no longer needed, delete this entire article and all links to it. -->
 
 {% data reusables.enterprise.single-organizations-enterprise-migration %}
 
-<!-- end expires 2025-06-30 -->
+<!-- end expires 2026-01-30 -->
 
 ## When should I create an enterprise account?
 
diff --git a/content/billing/tutorials/automate-usage-reporting.md b/content/billing/tutorials/automate-usage-reporting.md
@@ -32,7 +32,7 @@ When you call a `/usage` endpoint, you must specify the enterprise or organizati
 
 For more detailed information and an example call and response, see [Get billing usage report for an enterprise](/rest/enterprise-admin/billing?apiVersion=2022-11-28#get-billing-usage-report-for-an-enterprise) or [Get billing usage report for an organization](/rest/billing/enhanced-billing?apiVersion=2022-11-28#get-billing-usage-report-for-an-organization) .
 
-<!-- expires 2025-07-01 -->
+<!-- expires 2025-12-01 -->
 ## Migrating from the endpoints used for the previous billing platform
 
 The previous billing platform provided three different endpoints for usage data:
@@ -124,4 +124,4 @@ Example of the new response
 
 {% endrowheaders %}
 
-<!-- end expires 2025-07-01 -->
+<!-- end expires 2025-12-01 -->
diff --git a/content/github-models/github-models-at-scale/use-models-at-scale.md b/content/github-models/github-models-at-scale/use-models-at-scale.md
@@ -33,6 +33,8 @@ See [AUTOTITLE](/github-models/about-github-models).
 
 ## Best practices for using {% data variables.product.prodname_github_models %} at scale
 
+The following best practices can help you effectively use {% data variables.product.prodname_github_models %} across your organization.
+
 ### Compare and evaluate AI models for governance and compliance
 
 Review and compare available AI models against your company’s governance, data security, and compliance requirements. You can do this in any Models-enabled {% data variables.product.github %} repository or in the {% data variables.product.prodname_github_models %} catalog from the {% data variables.product.prodname_marketplace %} at https://github.com/marketplace?type=models. Your considerations may include:
@@ -113,7 +115,7 @@ Large software development projects often contain issues full of technical detai
          important questions.
      - role: user
        content: 'Summarize this issue, please - {% raw %}{{input}}{% endraw %}'
-   model: gpt-4o
+   model: openai/gpt-4o
    modelParameters:
      max_tokens: 4096
    ```
diff --git a/content/github-models/quickstart.md b/content/github-models/quickstart.md
@@ -22,7 +22,6 @@ This guide helps you try out models quickly in the playground, then shows you ho
 ## Step 1: Try models in the playground
 
 1. Go to **[https://github.com/marketplace/models](https://github.com/marketplace/models)**.
-
 1. In the playground, select at least one model from the dropdown menu.
 1. Test out different prompts using the **Chat** view, and compare responses from different models.
 1. Use the **Parameters** view to customize the parameters for the models you are testing, then see how they impact responses.
@@ -70,10 +69,9 @@ To call models programmatically, you’ll need:
 
 1. To try other models, change the value of the `model` field in the JSON payload to one from the [marketplace](https://github.com/marketplace/models).
 
-## Step 3: Run models in GitHub Actions
+## Step 3: Run models in {% data variables.product.prodname_actions %}
 
 1. In your repository, create a workflow file at `.github/workflows/models-demo.yml`.
-
 1. Paste the following workflow into the file you just created.
 
     ```yaml copy
@@ -118,13 +116,12 @@ This example shows how to send a prompt to a model and use the response in your
 {% data variables.product.prodname_github_models %} supports reusable prompts defined in `.prompt.yml` files. Once you add this file to your repository, it will appear in the Models page of your repository and can be run directly in the Prompt Editor and evaluation tooling. Learn more about [AUTOTITLE](/github-models/use-github-models/storing-prompts-in-github-repositories).
 
 1. In your repository, create a file named `summarize.prompt.yml`. You can save it in any directory.
-
 1. Paste the following example prompt into the file you just created.
 
     ```yaml copy
     name: Text Summarizer
     description: Summarizes input text concisely
-    model: gpt-4o-mini
+    model: openai/gpt-4o-mini
     modelParameters:
       temperature: 0.5
     messages:
@@ -139,11 +136,8 @@ This example shows how to send a prompt to a model and use the response in your
     ```
 
 1. Commit and push the file to your repository.
-
 1. Go to the **Models** tab in your repository.
-
 1. In the navigation menu, click **{% octicon "note" aria-hidden="true" aria-label="none" %} Prompts**, then click on the prompt file.
-
 1. The prompt will open in the prompt editor. Click **Run**. A right-hand sidebar will appear asking you to enter input text. Enter any input text, then click **Run** again in the bottom right corner to test it out.
 
    > [!NOTE]
@@ -154,13 +148,12 @@ This example shows how to send a prompt to a model and use the response in your
 Evaluations help you measure how different models respond to the same inputs so you can choose the best one for your use case.
 
 1. Go back to the `summarize.prompt.yml` file you created in the previous step.
-
 1. Update the file to match the following example.
 
    ```yaml copy
    name: Text Summarizer
    description: Summarizes input text concisely
-   model: gpt-4o-mini
+   model: openai/gpt-4o-mini
    modelParameters:
      temperature: 0.5
    messages:
@@ -190,11 +183,8 @@ Evaluations help you measure how different models respond to the same inputs so
    ```
 
 1. Commit and push the file to your repository.
-
 1. In your repository, click the **Models** tab. Then click **{% octicon "note" aria-hidden="true" aria-label="none" %} Prompts** and reopen the same prompt in the prompt editor.
-
 1. In the top left-hand corner, you can toggle the view from **Edit** to **Compare**. Click **Compare**.
-
 1. Your evaluation will be set up automatically. Click **Run** to see results.
 
    > [!TIP]
diff --git a/content/github-models/use-github-models/storing-prompts-in-github-repositories.md b/content/github-models/use-github-models/storing-prompts-in-github-repositories.md
@@ -8,11 +8,11 @@ versions:
   ghec: '*'
 ---
 
-Prompts can be stored as files directly within GitHub repositories. This unlocks the ability to view your prompts in an organized UI, share them with non-technical stakeholders, and run seamless iterations and comparisons on adjustments to models and prompts.
+Prompts can be stored as files directly within {% data variables.product.github %} repositories. This unlocks the ability to view your prompts in an organized UI, share them with non-technical stakeholders, and run seamless iterations and comparisons on adjustments to models and prompts.
 
 ## Benefits
 
-* Easy integration with the new suite of AI development tools directly on GitHub.
+* Easy integration with the new suite of AI development tools directly on {% data variables.product.github %}.
 * Simple and scalable from simple to complex use cases.
 * Uses a widely supported format, compatible with existing tools.
 
@@ -27,7 +27,7 @@ Example:
 ``` yaml copy
 name: Text Summarizer
 description: Summarizes input text concisely
-model: gpt-4o-mini
+model: openai/gpt-4o-mini
 modelParameters:
   temperature: 0.5
 messages:
diff --git a/content/migrations/overview/migration-paths-to-github.md b/content/migrations/overview/migration-paths-to-github.md
@@ -18,13 +18,6 @@ Some migration paths require tools that are only available with expert-led migra
 
 In our recommendations, we'll assume that you want the highest level of fidelity if possible, which includes source, history, and metadata.
 
-<!-- expires 2025-06-30 -->
-
-> [!NOTE]
-> Enterprise Cloud Importer (ECI) and the GraphQL endpoints for importing migration data to {% data variables.product.prodname_ghe_cloud %} from an archive are closing down on March 31, 2025. After this date, these tools can not be used to import repository data into GitHub's cloud-based products. We recommend using {% data variables.product.prodname_importer_proper_name %} (GEI). See [AUTOTITLE](/migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/about-github-enterprise-importer).
-
-<!-- end expires 2025-06-30 -->
-
 ## Migrations to {% data variables.product.prodname_dotcom_the_website %}
 
 You can review the scope and tooling for your migration to {% data variables.product.prodname_dotcom_the_website %}, which includes migrations to {% data variables.product.prodname_ghe_cloud %}. You can also review any additional information or caveats.
diff --git a/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md b/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md
@@ -38,14 +38,14 @@ To learn how to use organizations most effectively, see [AUTOTITLE](/organizatio
 
 ## Organizations and enterprise accounts
 
-<!-- expires 2025-06-30 -->
+<!-- expires 2026-01-30 -->
 
 <!-- When this expires, check with the stakeholder for release #4079 on whether or not the content is still needed -->
 
 {% ifversion ghec %}
-> [!NOTE] Currently, {% data variables.product.prodname_ghe_cloud %} customers who use a single organization are being automatically upgraded to an enterprise account at no additional cost. For details, see [AUTOTITLE](/admin/managing-your-enterprise-account/creating-an-enterprise-account#what-will-happen-after-i-upgrade-my-organization).
+> [!NOTE] {% data variables.product.prodname_ghe_cloud %} customers who use a single organization are being automatically upgraded to an enterprise account at no additional cost. For details, see [AUTOTITLE](/admin/managing-your-enterprise-account/creating-an-enterprise-account#what-will-happen-after-i-upgrade-my-organization).
 {% endif %}
-<!-- end expires 2025-06-30 -->
+<!-- end expires 2026-01-30 -->
 
 {% ifversion fpt %}
 Enterprise accounts are a feature of {% data variables.product.prodname_ghe_cloud %} that allow owners to centrally manage policy and billing for multiple organizations. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/organizations/collaborating-with-groups-in-organizations/about-organizations).
diff --git a/data/reusables/enterprise/create-an-enterprise-account.md b/data/reusables/enterprise/create-an-enterprise-account.md
@@ -1,7 +1,7 @@
-<!-- expires 2025-06-30 -->
+<!-- expires 2026-01-30 -->
 
 <!-- When this expires, check with the stakeholder for release #4079 on whether or not the content is still needed -->
 
 If you currently use {% data variables.product.prodname_ghe_cloud %} with a single organization, we encourage you to create an enterprise account.
 
-<!-- end expires 2025-06-30 -->
+<!-- end expires 2026-01-30 -->
diff --git a/data/reusables/enterprise/single-organizations-enterprise-migration.md b/data/reusables/enterprise/single-organizations-enterprise-migration.md
@@ -1,7 +1,7 @@
-<!-- expires 2025-06-30 -->
+<!-- expires 2026-01-30 -->
 
 <!-- When this expires, check with the stakeholder for release #4079 on whether or not the content is still needed -->
 
 > [!NOTE] Currently, {% data variables.product.prodname_ghe_cloud %} customers who use a single organization are being automatically upgraded to an enterprise account at no additional cost. For details, see [AUTOTITLE](/admin/managing-your-enterprise-account/creating-an-enterprise-account#what-will-happen-after-i-upgrade-my-organization).
 
-<!-- end expires 2025-06-30 -->
+<!-- end expires 2026-01-30 -->
