Clarify Codespaces billing for forks - #45373
Open
SR0725 wants to merge 1 commit into
Open
Conversation
Contributor
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
marked this pull request as ready for review
August 1, 2026 03:57
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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: