[pull] main from github:main

.github/workflows/changelog-agent.md

@@ -32,8 +32,7 @@ on:
         DOCS_BOT_PAT: ${{ secrets.DOCS_BOT_PAT_BASE }}
       with:
         script: |
-          // Default octokit uses github.token for in-repo (docs-internal) calls
-          const octokit = github;
+          // octokit (provided by github-script) uses github.token for in-repo (docs-internal) calls
           // Cross-repo octokit uses DOCS_BOT_PAT for docs-content and GraphQL calls
           const crossRepoOctokit = github.getOctokit(process.env.DOCS_BOT_PAT);
 

.github/workflows/index-general-search.yml

@@ -331,6 +331,36 @@ jobs:
           **Workflow file:** $FILE_URL
 
           This issue was automatically created by the \`$WORKFLOW_NAME\` workflow.
+
+          ---
+
+          ## Instructions for the issue analysis agent
+
+          These scraping failures are **almost never timeouts**. They are
+          almost always caused by Liquid/Markdown corruptions in the
+          translated source that make the page fail to render. Please do not
+          file this as a transient/timeout issue.
+
+          To investigate:
+
+          1. Pull the translation repos locally:
+             \`\`\`
+             npm run clone-translations
+             \`\`\`
+          2. Identify the specific corruptions with the canonical reporter
+             (verify the exact script name in \`package.json\` before running):
+             \`\`\`
+             npm run count-translation-corruptions
+             \`\`\`
+             The script writes a structured JSON report to stdout listing each
+             corrupted file, its location, the error message, and the
+             offending/illegal tag token when available.
+          3. **Open a pull request that fixes the corruptions** rather than
+             just commenting the findings on this issue. The issue body above
+             already lists the affected pages; the value the agent adds is
+             the fix. Where possible, fix the underlying pattern in
+             \`src/languages/lib/correct-translation-content.ts\` so the same
+             corruption is corrected on future syncs.
           EOF
           )
           gh issue create \

content/account-and-profile/concepts/personal-profile.md

@@ -54,7 +54,7 @@ To hide parts of your profile page, you can make your profile private. This also
 
 After making your profile private, you can still view all your information when you visit your own profile.
 
-For more information, see [AUTOTITLE](/account-and-profile/how-tos/setting-up-and-managing-your-github-profile/customizing-your-profile/setting-your-profile-to-private).
+For more information, see [AUTOTITLE](/account-and-profile/how-tos/profile-customization/setting-your-profile-to-private).
 
 ### Differences between private and public profiles
 
@@ -91,5 +91,5 @@ You can control the visibility of specific profile elements or set your entire p
 ## Next steps
 
 * For a general tutorial on personalizing your profile, see [AUTOTITLE](/account-and-profile/tutorials/personalize-your-profile).
-* For more specific profile customization, see [AUTOTITLE](/account-and-profile/how-tos/setting-up-and-managing-your-github-profile).
+* For more specific profile customization, see [AUTOTITLE](/account-and-profile/how-tos).
 * For reference information, see [AUTOTITLE](/account-and-profile/reference/profile-reference).

content/account-and-profile/get-started/account.md

@@ -25,10 +25,10 @@ If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}
 
 ## Next steps
 
-* For conceptual information about accounts, see [AUTOTITLE](/account-and-profile/concepts/personal-account-management).
+* For conceptual information about accounts, see [AUTOTITLE](/account-and-profile/concepts/account-management).
 * For information about managing your account, see [AUTOTITLE](/account-and-profile/how-tos/setting-up-and-managing-your-personal-account-on-github).
 * For reference information, see [AUTOTITLE](/account-and-profile/reference/personal-account-reference).
 {%- ifversion ghec %}
 * For information about {% data variables.enterprise.prodname_managed_users %}, see [AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users).
-* For information about managing multiple accounts, see [AUTOTITLE](/account-and-profile/concepts/personal-account-management#about-management-of-multiple-accounts).
+* For information about managing multiple accounts, see [AUTOTITLE](/account-and-profile/concepts/account-management#about-management-of-multiple-accounts).
 {%- endif %}

content/account-and-profile/how-tos/contribution-settings/viewing-contributions-on-your-profile.md

@@ -22,7 +22,7 @@ category:
 
 ## Prerequisites
 
-Before you view contributions on your profile, you should understand what counts as a contribution, and what other information your profile displays. See [AUTOTITLE](/account-and-profile/concepts/contributions-visible-on-your-profile).
+Before you view contributions on your profile, you should understand what counts as a contribution, and what other information your profile displays. See [AUTOTITLE](/account-and-profile/concepts/contributions-on-your-profile).
 
 ## Viewing contributions in a specific time range
 

content/account-and-profile/how-tos/profile-customization/setting-your-profile-to-private.md

@@ -21,5 +21,5 @@ category:
 
 ## Next steps
 
-* For more information about private profiles, see [AUTOTITLE](/account-and-profile/concepts/about-your-profile#private-profiles).
+* For more information about private profiles, see [AUTOTITLE](/account-and-profile/concepts/personal-profile#private-profiles).
 * For reference information, see [AUTOTITLE](/account-and-profile/reference/profile-reference#limitations-of-private-profiles).

content/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens.md

@@ -208,6 +208,9 @@ Repository permissions work for both user and organization resource owners.
 | `artifact_metadata` | Artifact Metadata | `read`, `write` |
 | {% endif %} |
 | `attestations` | Attestations | `read`, `write` |
+| {% ifversion code-quality %} |
+| `code_quality` | Code quality | `read`, `write` |
+| {% endif %} |
 | `security_events` | Code scanning alerts | `read`, `write` |
 | `codespaces` | Codespaces | `read`, `write` |
 | `codespaces_lifecycle_admin` | Codespaces lifecycle admin | `read`, `write` |

content/billing/concepts/product-billing/github-codespaces.md

@@ -35,6 +35,11 @@ In addition, any prebuilt codespaces are generated using actions minutes, see [A
 
 The compute time for a codespace is the length of time for which that codespace is active. Total use of compute time for each processor type is calculated by summing the time used by all codespaces billable to a particular account. These totals are reported to the billing service every hour, and are billed monthly.
 
+* **Compute time:** Your included compute hours reset to the full amount at the start of each billing cycle. Compute usage is charged to the account that owns the codespace.
+* **Storage:** Storage charges accumulate throughout the month based on hourly usage. Your accrued storage charges reset to zero at the start of each billing cycle.
+
+For more information about billing cycles, see [AUTOTITLE](/billing/concepts/billing-cycles).
+
 ### Storage volume for codespaces
 
 Storage is a time-based measurement of the amount of storage used in GB-hours. The storage measured for codespaces includes:

content/billing/how-tos/set-up-payment/manage-payment-info.md

@@ -24,7 +24,7 @@ category:
   - Set up payment
 ---
 
-The payment methods available depend on your account type. Enterprise and organization accounts have more payment options than personal accounts. Invoiced enterprise accounts make their payments using other methods. For more information, see [AUTOTITLE](/billing/reference/supported-payment-methods).
+The payment methods available depend on your account type. Enterprise and organization accounts have more payment options than personal accounts. Invoiced enterprise accounts make their payments using other methods. For more information, see [AUTOTITLE](/billing/reference/payment-methods).
 
 ## Managing payment information
 

content/billing/reference/index.md

@@ -20,6 +20,6 @@ children:
   - /product-and-sku-names
   - /product-usage-included
   - /roles-for-visual-studio
-  - /supported-payment-methods
+  - /payment-methods
 contentType: reference
 ---

content/billing/reference/payment-methods.md

@@ -0,0 +1,41 @@
+---
+title: Payment methods
+shortTitle: Payment methods
+intro: 'Reference information for supported payment methods for {% data variables.product.github %}.'
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+contentType: reference
+category:
+  - Set up payment
+redirect_from:
+  - /billing/reference/supported-payment-methods
+---
+
+The payment methods available to you depend on your account type and the products you use.
+
+## Self-serve accounts
+
+Self-serve accounts can use the following payment methods:
+
+* Credit card
+* PayPal
+* Azure Subscription ID (not personal accounts)
+
+## Invoiced accounts
+
+Invoiced accounts can use different payment methods for volume-licensed products (such as {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_GH_advanced_security %}) and metered products (such as {% data variables.product.prodname_github_codespaces %}). You can combine payment methods for different product types. For example, you can use invoice for volume products and Azure Subscription ID for metered products.
+
+| Payment method | Volume products | Metered products |
+|---|---|---|
+| Credit card | {% octicon "x" aria-label="Not supported" %} | {% octicon "check" aria-label="Supported" %} |
+| PayPal | {% octicon "x" aria-label="Not supported" %} | {% octicon "check" aria-label="Supported" %} |
+| Azure Subscription ID | {% octicon "x" aria-label="Not supported" %} | {% octicon "check" aria-label="Supported" %} |
+| Invoice | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} |
+| Prepaid credits | {% octicon "check" aria-label="Supported" %} | {% octicon "x" aria-label="Not supported" %} |
+| Purchase order | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} |
+| ACH | {% octicon "x" aria-label="Not supported" %} | {% octicon "check" aria-label="Supported" %} |
+
+> [!NOTE]
+> For purchase orders, contact [{% data variables.product.github %}'s Sales team](https://github.com/enterprise/contact?scid=&utm_campaign=2023q3-site-ww-PremiumSupport&utm_content=Premium+Support&utm_medium=referral&utm_source=github).