Clarify Codespaces billing for forks - #45373
Conversation
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. The table shows the files in the
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server 🤖 This comment is automatically generated. |
|
@SR0725 Looks good, thanks for the update! |
|
Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡ |
OpenAI Codex generated this pull request. External contributors cannot apply repository labels, so a maintainer will need to add
llm-generated.Why:
Fixes #41324
The billing conditions currently imply that any personal fork of an organization repository can produce an organization-paid codespace. The issue confirms that this applies only to organization-owned forks.
What's being changed:
The reusable now says that a codespace can come from an organization's repository or an organization-owned fork. This keeps personal forks owned by outside collaborators out of the organization-paid case.
SME review needed: Please confirm the billing boundary in the edited second bullet. The wording follows the engineer-backed suggestion in #41324.
Validation:
npm run lint-content -- --paths data/reusables/codespaces/when-an-org-pays.mdnpm run buildCHANGED_FILES=content/codespaces/managing-codespaces-for-your-organization/choosing-who-owns-and-pays-for-codespaces-in-your-organization.md npm run test -- src/content-render/tests/render-changed-and-deleted-files.tsCheck off the following: