docs(repo): mark the Free-plan environment split as observed, cite GitHub Docs - #124
Open
marcusjacobson wants to merge 2 commits into
Open
docs(repo): mark the Free-plan environment split as observed, cite GitHub Docs#124marcusjacobson wants to merge 2 commits into
marcusjacobson wants to merge 2 commits into
Conversation
…tHub Docs The GitHub-plan note in getting-started section 2 stated 'deployment branch policies work on all plans' as bare fact. GitHub's own availability notes say something narrower — Free plans 'can only configure environments for public repositories', with no per-feature breakdown — so the branch-policy half is empirically observed behavior (REST accepted deployment_branch_policy on a Free private repo, 2026-07-16) that the documentation does not guarantee. Reworded the note to separate observed from documented and added the citation with its as-of date, per the grounding rule that capability claims cite the authoritative page. Interim posture guidance unchanged. index.html embeds regenerated. See: https://docs.github.com/en/actions/how-tos/deploy/configure-and-manage-deployments/manage-environments Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
Owner GateReady for lab-owner approval. All checks are passing and this PR carries To approve, run This comment is maintained automatically by the |
1 similar comment
Contributor
Owner GateReady for lab-owner approval. All checks are passing and this PR carries To approve, run This comment is maintained automatically by the |
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
Summary
Docs plane: correct the provenance of the GitHub Free-plan environment note in Getting started §2 — the deployment-branch-policy availability on Free private repos is empirically observed behavior, not something GitHub's documentation guarantees — and add the missing citation. Post-merge follow-up from the PR #123 downstream verification (the operations repo's empirical finding).
Plane and scope
infra/**(control plane, Bicep)data-plane/**(data plane, YAML)scripts/**(data-plane apply logic).github/workflows/**(CI/CD)docs/**orREADME.md(documentation)Also
index.html(regenerated embeds — required whenever an embedded doc changes) andCHANGELOG.md. Single plane: docs only.Change detail
> [!NOTE]GitHub-plan block in docs/getting-started.md §2: the claim "deployment branch policies work on all plans" becomes an explicitly observed result (REST accepteddeployment_branch_policyon a GitHub Free private repo, verified 2026-07-16; required reviewers rejected with HTTP 422), contrasted with what GitHub actually documents — "Users with GitHub Free plans can only configure environments for public repositories" and "Some features for environments have no or limited availability for private repositories", with no per-feature breakdown as of 2026-07-16 (Managing environments for deployment). Interim-posture guidance (branch policy + per-environment OIDC subject per ADR 0010 §3) unchanged.index.htmlembedded doc snapshots (Update-LandingPageEmbeds.ps1;-Checkpasses).Validation evidence
Security review
publicNetworkAccesschangesRollback plan
Revert the single docs commit(s); no state, workflow, or script behavior is touched.
Breaking / destructive
None — prose-only.
🤖 Generated with Claude Code