docs: the repository is public - #10
Conversation
Two documents asserted the repo was private, which stopped being true today. pages.yml warned that Pages needs a paid plan on a private repo. That no longer applies, but the note is kept rather than deleted: reverting to private would silently reintroduce a 404 on deploy, and a comment explaining why something works is more useful than its absence. AGENTS.md's review-authority section said "single-maintainer private repository". The single-maintainer part is what the argument rests on -- there is no reviewer pool -- so only the visibility claim is corrected. Public changes who can read the repo, not who reviews it. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Updates repository documentation to reflect that the project is now public, while preserving operational notes that would matter if visibility is reverted later.
Changes:
- Adjust
AGENTS.mdreview-authority wording to remove the “private repository” claim and clarify the impact of becoming public. - Update the GitHub Pages workflow header comment to reflect that Pages is now free on a public repo, while keeping the historical/private-repo warning for future reference.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| AGENTS.md | Corrects the repository visibility statement in the review-authority section, clarifying read access vs review authority. |
| .github/workflows/pages.yml | Updates the Pages requirements comment to reflect the repo being public while preserving the private-repo caveat. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
Code Review
This pull request updates the AGENTS.md file to reflect that the repository is now public, clarifying that this change only affects who can read the repository, not who reviews it. The reviewer suggested removing the specific date of the public transition to keep the documentation concise and free of temporal noise, providing a concrete suggestion to simplify the text and cross-reference with CONTRIBUTING.md to prevent documentation drift.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
Adopts Gemini's comment on PR #10. AGENTS.md is an operational instruction file, and "as of 2026-07-20" does not help an agent operate -- it is temporal noise in a document read for rules, not history. The parenthetical now states the rule directly. The date is deliberately KEPT in pages.yml, where the context is different: there it explains why a paid-plan note exists at all and warns that reverting to private would silently reintroduce a 404 on deploy. That is operationally relevant to whoever next edits that workflow. On the cross-reference point: CONTRIBUTING.md already points at AGENTS.md Shipping for merge authority (added in #1, for exactly this drift reason), and the two do not contradict -- CONTRIBUTING states the one-reviewer-minimum rule and AGENTS explains who that reviewer is and when to stop and ask. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Two documents asserted the repo was private, which stopped being true today.
pages.ymlwarned Pages needs a paid plan on a private repo. No longer applies, but the note is kept rather than deleted — reverting to private would silently reintroduce a 404 on deploy.AGENTS.md's review-authority section said "single-maintainer private repository". The single-maintainer part is what the argument rests on, so only the visibility claim is corrected. Public changes who can read the repo, not who reviews it.actionlintandmarkdownlintclean. No code changes.