github · docs-bot · Aug 10, 2026 · Aug 10, 2026 · Aug 10, 2026 · Aug 10, 2026
diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md
@@ -82,7 +82,7 @@ For complete style guidance, see our [style guide](https://docs.github.com/en/co
 
 **Make changes locally:** 
 1. Fork the repository (see [official forking guide](https://docs.github.com/en/contributing))
-2. Install Node.js at the version specified in `.node-version` (see [development guide](../contributing/development.md))
+2. Install Node.js at the version specified in `package.json` (see [development guide](../contributing/development.md))
 3. Create a working branch and start with your changes
 
 ### Commit your update

diff --git a/.github/instructions/code.instructions.md b/.github/instructions/code.instructions.md
@@ -50,7 +50,6 @@ Some test suites depend on fixture content or external services. These suites ha
 
 ```shell
 npm run test:article-api
-npm run test:changelogs
 npm run test:fixtures
 npm run test:landings
 npm run test:languages    # requires Elasticsearch running

diff --git a/config/moda/secrets/ci/secrets.yml b/config/moda/secrets/ci/secrets.yml
@@ -7,21 +7,3 @@ secrets:
     playbook: ''
     externally_usable: true
     kind: latest_at_deployment_start
-  DOCS_BOT_APP_CLIENT_ID:
-    owner: docs-engineering
-    type: github_app
-    externally_usable: false
-    playbook: ''
-    kind: latest_at_deployment_start
-  DOCS_BOT_APP_ID:
-    owner: docs-engineering
-    type: github_app
-    externally_usable: false
-    playbook: ''
-    kind: latest_at_deployment_start
-  DOCS_BOT_APP_PRIVATE_KEY:
-    owner: docs-engineering
-    type: github_app
-    externally_usable: false
-    playbook: ''
-    kind: latest_at_deployment_start
diff --git a/config/moda/secrets/production/secrets.yml b/config/moda/secrets/production/secrets.yml
@@ -14,21 +14,6 @@ secrets:
     type: salt
     owner: '@github/docs-engineering'
     externally_usable: true
-  DOCS_BOT_APP_CLIENT_ID:
-    kind: latest_at_deployment_start
-    type: github_app
-    owner: '@github/docs-engineering'
-    externally_usable: true
-  DOCS_BOT_APP_ID:
-    kind: latest_at_deployment_start
-    type: github_app
-    owner: '@github/docs-engineering'
-    externally_usable: true
-  DOCS_BOT_APP_PRIVATE_KEY:
-    kind: latest_at_deployment_start
-    type: github_app
-    owner: '@github/docs-engineering'
-    externally_usable: true
   DOCS_BOT_PAT_BASE:
     kind: latest_at_deployment_start
     type: github_pat

diff --git a/content/admin/overview/setting-up-a-trial-of-github-enterprise-cloud.md b/content/admin/overview/setting-up-a-trial-of-github-enterprise-cloud.md
@@ -6,39 +6,33 @@ redirect_from:
   - /github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud
   - /github/getting-started-with-github/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud
   - /get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud
+  - /enterprise-onboarding/getting-started-with-your-enterprise/setting-up-a-trial-of-github-enterprise
+  - /enterprise-onboarding/getting-started-with-your-enterprise/ending-a-trial-of-github-enterprise
 versions:
   ghec: '*'
-  ghes: '*'
 shortTitle: Enterprise Cloud trial
 category:
   - Get started with GitHub Enterprise
+docsTeamMetrics:
+  - enterprise-onboarding
 ---
 
-{% data reusables.enterprise.about-ghec %} See [AUTOTITLE](/enterprise-cloud@latest/admin/overview/about-github-enterprise-cloud).
+After you've decided which type of enterprise is right for you (see [AUTOTITLE](/admin/concepts/enterprise-fundamentals/choose-an-enterprise-type)), you can set up your trial.
 
-To set up a trial, you must be signed in to a personal account. If you don't have a personal account, see [AUTOTITLE](/account-and-profile/how-tos/account-management/creating-an-account-on-github).
+If you choose an {% data variables.enterprise.prodname_emu_enterprise %}, you'll also choose whether to create your trial on {% data variables.product.prodname_dotcom_the_website %} or {% data variables.enterprise.data_residency_site %}. Trials on {% data variables.product.prodname_dotcom_the_website %} include {% data variables.product.prodname_GHAS %} features. Trials on {% data variables.enterprise.data_residency_site %} support regional data residency, but some features are not available. See [AUTOTITLE](/enterprise-cloud@latest/admin/data-residency/feature-overview-for-github-enterprise-cloud-with-data-residency#currently-unavailable-features).
 
 <a href="https://github.com/account/enterprises/new?ref_product=ghec&ref_type=trial&ref_style=button&ref_plan=enterprise" target="_blank" class="btn btn-primary mt-3 mr-3 no-underline"><span>Set up a trial of {% data variables.product.prodname_ghe_cloud %}</span> {% octicon "link-external" height:16 aria-label="link-external" %}</a>
 
-## About enterprise types
-
-{% data reusables.enterprise.enterprise-types %}
-
-{% data reusables.enterprise.emus-trial-content %}
-
-## What is included in the trial?
+## Features included in the trial?
 
 The trial lasts for **{% data reusables.enterprise.ghec-trial-length %} days** and includes the following features.
 
 * Access to **most** {% data variables.product.prodname_ghe_cloud %} features.
-* {% data variables.product.prodname_GH_cs_and_sp %} ({% data variables.product.prodname_dotcom_the_website %} trials only)
-* Access to the **new billing platform**.{% ifversion enhanced-billing-platform %} See [AUTOTITLE](/billing/get-started/introduction-to-billing).{% endif %}
 * An **enterprise account**, which allows you to manage multiple organizations. See [AUTOTITLE](/enterprise-cloud@latest/get-started/learning-about-github/types-of-github-accounts).
 * Up to **50 licenses** to grant access to users.
+* {% data variables.product.prodname_GH_cs_and_sp %} ({% data variables.product.prodname_dotcom_the_website %} trials only)
 * Up to 3,000 minutes of standard {% data variables.product.prodname_dotcom %}-hosted runners.
 
-Your trial **won't** include access to {% data variables.product.prodname_ghe_server %}. To test this, contact {% data variables.contact.contact_enterprise_sales %}.
-
 ## Features not included in the trial
 
 * {% data variables.product.prodname_github_codespaces %}
@@ -49,6 +43,7 @@ Your trial **won't** include access to {% data variables.product.prodname_ghe_se
 * {% data variables.product.prodname_github_connect %}
 * {% data variables.large_files.product_name_long %}
 * For {% data variables.product.prodname_actions %}, increased minutes, job concurrency, and {% data variables.actions.hosted_runners %}
+* Access to {% data variables.product.prodname_ghe_server %}. To test this, contact {% data variables.contact.contact_enterprise_sales %}.
 
 If you invite an existing organization into your trial enterprise, **all of these features will be disabled**. If you remove the organization from the enterprise, the features will be re-enabled.
 
@@ -60,8 +55,12 @@ You do not need to provide a payment method to start a trial.
 
 After you set up your trial, you can explore {% data variables.product.prodname_ghe_cloud %} by following the suggested tasks on the "Getting started" tab of your enterprise account.
 
+### Organizations in your trial
+
 You can create up to **three new organizations** in the trial enterprise, or transfer any number of existing organizations.
 
+When transferring existing organizations, keep in mind these restrictions:
+
 * You cannot transfer organizations if you selected an {% data variables.enterprise.prodname_emu_enterprise %}.
 * You cannot transfer organizations that have free or paid {% data variables.product.prodname_marketplace %} apps. Free apps are supported for new organizations in the trial.
 * You cannot transfer organizations that are already owned by another enterprise.
@@ -76,48 +75,15 @@ You can end your trial at any time by purchasing {% data variables.product.prodn
 
 {% data variables.product.prodname_enterprise %} trial accounts are automatically deleted 90 days after the trial period ends if the account has not been converted to a paid account.
 
-If you **purchase {% data variables.product.prodname_enterprise %}**:
-
-* You can use usage-based billing for {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_GHAS %} products, which means you pay monthly for the number of licenses you use. You will not need to buy a predefined number of licenses in advance. See [AUTOTITLE](/billing/concepts/enterprise-billing/usage-based-licenses).
-
-  If you did not set up a free trial and you want to use usage-based billing to pay for {% data variables.product.prodname_GHAS %} products after the {% data variables.product.prodname_ghe_cloud %} trial ends, contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
-
-* You can generate a {% data variables.product.prodname_ghe_server %} license file for the same quantity of users who are consuming a {% data variables.product.prodname_ghe_cloud %} license.
+### If you cancel your trial
 
-If you **cancel your trial**:
+You can cancel your trial anytime in the "Danger zone" section of your enterprise settings.
 
 * Organizations that you transferred into the enterprise are removed and reverted to their previous plans and settings.
 * Enterprise owners and members lose access to the enterprise account and any organizations that you created during the trial.
 
-If your **trial expires**:
+### If your trial expires
 
 * Organizations that you transferred into the enterprise are removed and reverted to their previous plans and settings.
 * Enterprise owners and members retain access to the enterprise account and organizations created during the trial in a downgraded state, allowing you to either upgrade to {% data variables.product.prodname_enterprise %} or move assets elsewhere.
 * You can delete an expired trial to remove people's access to the enterprise and organizations created during the trial.
-
-For more information about the effects of downgrading an organization, see [AUTOTITLE](/enterprise-cloud@latest/billing/how-tos/manage-plan-and-licenses/downgrade-plan#downgrading-your-organizations-plan).
-
-## Ending your trial
-
-You can end a trial by purchasing {% data variables.product.prodname_enterprise %} or by canceling the trial. If a trial has expired, you can delete the trial.
-
-### Purchasing {% data variables.product.prodname_enterprise %}
-
-You can purchase {% data variables.product.prodname_enterprise %} at any time during the trial.
-
-{% data reusables.enterprise-accounts.access-enterprise %}
-1. To end the trial period and purchase {% data variables.product.prodname_enterprise %}, click **Activate Enterprise** in the blue banner at the top of the page.
-
-### Canceling or deleting a trial
-
-You can cancel a trial at any time. Once the trial has expired, you can delete the trial.
-
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-1. Under **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**, click **General**.
-1. At the bottom of the page, in the "Danger zone" section, click **Cancel trial** or **Delete trial**.
-
-## Further reading
-
-* [AUTOTITLE](/admin/concepts/enterprise-best-practices/organize-work)
-* [{% data variables.product.prodname_roadmap %}]({% data variables.product.prodname_roadmap_link %})
diff --git a/content/billing/how-tos/set-up-payment/india-one-time-payments.md b/content/billing/how-tos/set-up-payment/india-one-time-payments.md
@@ -1,22 +1,23 @@
 ---
-title: One-time payments for customers in India
-intro: Customers in India who have been impacted by the Reserve Bank of India's recurring payment regulation can now make one-time payments for their GitHub subscriptions and services.
+title: Payments for customers in India
+intro: Customers in India who have been impacted by the Reserve Bank of India's recurring payment regulation can use RBI-compliant payment mandates with eligible credit card payment methods or make one-time payments for their {% data variables.product.github %} subscriptions and services.
+allowTitleToDifferFromFilename: true
 redirect_from:
   - /early-access/billing/india-rbi-regulation
   - /billing/managing-billing-for-your-github-account/one-time-payments-for-customers-in-india
   - /billing/managing-the-plan-for-your-github-account/one-time-payments-for-customers-in-india
 versions:
   fpt: '*'
   ghec: '*'
-shortTitle: India one-time payments
+shortTitle: Payments in India
 contentType: how-tos
 category:
   - Set up payment
 ---
 
 ## About the Reserve Bank of India's recurring payments regulation
 
-A new payments regulation from the Reserve Bank of India (RBI) recently came into effect. This regulation places additional requirements on recurring online transactions and has prevented some {% data variables.product.company_short %} customers in India from making recurring payments. Customers using payment methods issued in India for any recurring transactions on {% data variables.product.github %} may find that their payments are declined by their banks or card issuers. For more information, see [the RBI's press release](https://www.rbi.org.in/Scripts/BS_PressReleaseDisplay.aspx?prid=51353).
+The Reserve Bank of India's (RBI) recurring payments regulation places additional requirements on recurring online transactions. Customers using payment methods issued in India for recurring transactions on {% data variables.product.github %} may find that their payments are declined by their banks or card issuers. For more information, see [the RBI's press release](https://www.rbi.org.in/Scripts/BS_PressReleaseDisplay.aspx?prid=51353).
 
 The regulation applies to all recurring transactions, including:
 
@@ -26,34 +27,38 @@ The regulation applies to all recurring transactions, including:
 * Git Large File Storage purchases
 * {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, and {% data variables.product.prodname_github_codespaces %} consumption
 
-In order to minimize disruption, recurring payments for our affected customers were paused on October 29th, 2021. Paid features and services have remained available to customers impacted by the RBI regulation.
+## About recurring payments on {% data variables.product.company_short %}
+
+{% data variables.product.company_short %} supports RBI-compliant payment mandates for customers in India with eligible credit card payment methods. A payment mandate allows {% data variables.product.company_short %} to automatically charge your saved payment method for recurring payments without manual action during each billing cycle.
+
+You can continue to save and remove payment methods the same way. For more information, see [AUTOTITLE](/billing/how-tos/set-up-payment/manage-payment-info).
+
+If your saved payment method cannot be charged automatically, you may need to make a one-time payment for the current billing cycle.
 
 ## About one-time payments on {% data variables.product.company_short %}
 
-As we work with our payment gateway provider to meet the new requirements, we are providing a temporary one-time payment option for impacted customers in India. From February 15th 2022, {% data variables.product.company_short %} customers in India who have been affected by the new RBI regulation will be able to make one-time payments on their regular billing cycle cadence.
+If you have been impacted by the RBI regulation and {% data variables.product.company_short %} cannot automatically charge your saved payment method, you can make a one-time payment on your regular billing cycle cadence.
 
 ### For customers on monthly billing
 
-Customers on monthly billing plans will be able to make a one-time payment on the same day their billing cycle usually renews. For example, if you're usually billed on the 7th of each month, you will now be able to make a one-time payment from your account from the 7th of each month. Your first one-time payment will also include any accrued usage from October 2021 onwards.
+Customers on monthly billing plans can make a one-time payment on the same day their billing cycle usually renews. For example, if you're usually billed on the 7th of each month, you can make a one-time payment from your account from the 7th of each month.
 
 If you are currently billed monthly, and would like to switch to yearly billing, you can reduce the frequency of your one-time payments. For more information, see [AUTOTITLE](/billing/concepts/billing-cycles).
 
 ### For customers on yearly billing
 
-If you are billed yearly, and your renewal date was between October 1st, 2021 and February 14th, 2022, you will be able to make a one-time payment for your annual subscriptions from February 15th. This initial payment will include the prorated outstanding cost of your subscription for the period since your previous billing cycle ended.
-
-If your billing cycle is due to renew after February 15th, we will attempt to take the recurring payment. If the payment attempt is declined, you will then be able to make a one-time payment through your account's billing page.
+If you are billed yearly, we will attempt to take the recurring payment when your billing cycle renews. If the payment attempt is declined, you can make a one-time payment through your account's billing page.
 
-In the meantime, we are actively working with our payment partners to restore recurring payments for impacted customers. For more information or questions, you can contact {% data variables.contact.contact_support %}.
+For more information or questions, you can contact {% data variables.contact.contact_support %}.
 
 ### Impact to {% data variables.product.prodname_sponsors %}
 
-Existing sponsorships will remain in place during this period and maintainers will continue to be paid out as expected. Payments for the accrued sponsorship amounts from the funding account will be collected at the same time as other accrued charges.
+Maintainers will continue receiving sponsorship payouts without interruption. Sponsorship charges will appear alongside other charges on the funding account.
 
 ## Making a one-time payment for a {% data variables.product.github %} subscription
 
 > [!NOTE]
-> Affected customers will receive an email notification with a link to their billing settings when payment is due. Two further reminder emails will be sent 7 and 14 days later if payment has not been made. After 14 days, paid features and services will be locked until payment is made.
+> Impacted customers will receive an email notification with a link to their billing settings when payment is due. Two further reminder emails will be sent 7 and 14 days later if payment has not been made. After 14 days, paid features and services will be locked until payment is made.
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.billing_plans_payment %}