Skip to content

docs: apply Matt's review notes from #18 - #21

Merged
aljo242 merged 1 commit into
mainfrom
docs/matt-review-followups
Oct 1, 2026
Merged

aljo242 merged 1 commit into
mainfrom
docs/matt-review-followups

Conversation

@aljo242

@aljo242 aljo242 commented Oct 1, 2026

Copy link
Copy Markdown
Contributor

Two readability fixes Matt raised on #18 after it merged.

The seven-days-early creation read as a callback to something not yet said, and the August walkthrough did not announce itself as an example.

The seven-days-early creation of the next month's repositories was written as a
callback, but that sentence is the first time the policy mentions it. States it
as new information and says what it is for.

Marks the August walkthrough as an example, which was not obvious on a first
read.
@aljo242
aljo242 requested a review from a team as a code owner October 1, 2026 20:04
@greptile-apps

greptile-apps Bot commented Oct 1, 2026 •

Copy link
Copy Markdown

RetriggerConfidence Score: 5/5

[Low risk] Clarifies security policy documentation wording.

The PR appears safe to merge.

Summary

The PR clarifies why the next month’s private repository set is created before the month begins and labels the August timeline as an example.

  • Both edits preserve the existing disclosure schedule.

Reviews (1) · Last reviewed commit: "docs: apply Matt's review notes from #18"

@aljo242
aljo242 merged commit 2c5970a into main Oct 1, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants