Skip to content

Clarify Codespaces billing for forks - #45373

Merged
Sharra-writes merged 2 commits into
github:mainfrom
SR0725:docs/clarify-codespaces-fork-ownership
Aug 7, 2026
Merged

Clarify Codespaces billing for forks#45373
Sharra-writes merged 2 commits into
github:mainfrom
SR0725:docs/clarify-codespaces-fork-ownership

Conversation

@SR0725

@SR0725 SR0725 commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

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.md
  • npm run build
  • CHANGED_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.ts

Check off the following:

  • A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
  • The changes in this PR meet the docs fundamentals that are required for all content.
  • All CI checks are passing and the changes look good in the review environment.

@github-actions

github-actions Bot commented Aug 1, 2026

Copy link
Copy Markdown
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 links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source Review Production What Changed
codespaces/managing-codespaces-for-your-organization/choosing-who-owns-and-pays-for-codespaces-in-your-organization.md fpt
ghec
fpt
ghec
from reusable

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

@github-actions github-actions Bot added the triage Do not begin working on this issue until triaged by the team label Aug 1, 2026
@SR0725
SR0725 marked this pull request as ready for review August 1, 2026 03:57
@Sharra-writes Sharra-writes added content This issue or pull request belongs to the Docs Content team Codespaces Content relating to GitHub Codespaces and removed triage Do not begin working on this issue until triaged by the team labels Aug 7, 2026
@Sharra-writes

Copy link
Copy Markdown
Contributor

@SR0725 Looks good, thanks for the update!

@Sharra-writes
Sharra-writes added this pull request to the merge queue Aug 7, 2026
Merged via the queue into github:main with commit e0202da Aug 7, 2026
40 checks passed
@github-actions

github-actions Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Codespaces Content relating to GitHub Codespaces content This issue or pull request belongs to the Docs Content team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Clarify billing-scope difference between members and collaborators on org-owned codespaces

2 participants