Repository navigation
docs: ADR-0017 and the repository's settings since it opened - #61
Conversation
Decided by the project lead on 2026-11-18. The repository is public from that day, before the trademark review of the name (issue #4). The review is done before version 0.1 is released, and if it fails the project is renamed by a new decision before any release. It amends ADR-0001, decision 8, and the third consequence of ADR-0003; neither file is changed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Madraka <8898640+Madraka@users.noreply.github.com>
docs/repository.md says what GitHub holds today, each setting read through the API on 2026-11-18: - the repository is public; - the two rulesets are active, and `main` also has a code scanning gate; - secret scanning with push protection, private vulnerability reporting and code scanning (extended suite) are on; - outside contributors' fork workflows wait for approval; - auto-merge, immutable releases and Discussions are on; - the environment `release` waits for the lead and for tags `v*`; - no self-hosted runner, and 90 days of retention. It also records what GitHub did not give (non-provider patterns and validity checks), how the repository opened, and what is open: the organisation does not require two-factor sign-in, the name review, and that nothing compares the ruleset files with GitHub. .github/rulesets/main.json is now identical to ruleset 27536582, code scanning rule and the three defaults GitHub adds included. The issue forms get a link to Discussions for questions. docs/status.md moves the repository's protections from section 2 to section 1. Refs #5 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Madraka <8898640+Madraka@users.noreply.github.com>
|
audit: one sentence to correct, then pass Read: every changed line. The ruleset file was compared with what GitHub holds for ruleset 27536582 (name, target, enforcement, conditions, bypass, rules): identical. Each setting in section 2 of To correct before this merges, because an accepted record cannot be changed afterwards:
Found to hold:
Not blocking: the milestone "Before the repository is public" keeps its name though the day has passed; #5 and #6 are still in it. I will rename it when #5 closes. |
…ode scanning was not asked for Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Madraka <8898640+Madraka@users.noreply.github.com>
|
Corrected in b8fab73: the Context of ADR-0017 now names the four protections GitHub refused on 2026-11-18, each with its answer, and says code scanning was not asked for while the repository was private. No other line changed. Ready for audit once CI is green. |
|
audit: pass Read at b8fab73. The one sentence I asked for is corrected: the Context of ADR-0017 now names the four protections GitHub refused while the repository was private, each with the answer it gave, and says that code scanning was not asked for and was left for the day the repository opened. That matches what happened. The commit changes that one line and nothing else. Everything read before still holds: The required checks are still running on this head. Merge when they are green; the ruleset holds the merge until then. |
What and why
The repository opened on 2026-11-18, and the documents still described a private one.
ADR-0017, accepted by the project lead on 2026-11-18. The repository is public before the trademark review of the name (Review the name "Podbay" for trademark use before the repository is public #4). The review is done before version 0.1, and the project is renamed by a new decision if it fails. It amends ADR-0001 (decision 8) and ADR-0003's third consequence. Neither file is edited, since an accepted record is never changed. The ADR index says what it amends.
docs/repository.md, sections 1 to 4, say what GitHub holds now. Every setting was read through the API today:
release(the lead's review, tagsv*);The page also records:
.github/rulesets/main.jsonis identical to ruleset 27536582, as compared by a script. That includes the code scanning rule and three defaults GitHub adds to the pull request rule.docs/status.md moves the repository's protections from section 2 (not yet) to section 1. The README link and the issue chooser follow: the chooser gets a link to Discussions for questions.
Refs #5. The one condition of #5 that is not met is the name review, and ADR-0017 makes it a condition of version 0.1 instead. Closing #5 is left to the lead.
Not verified
SECURITY.md's report link opens the form for someone signed out (step 6 of the old plan). I could not check that from here.Checklist
pnpm checkis green (documents and settings only;pnpm test:workerdnot run, nothing it covers changed).git commit -s).🤖 Generated with Claude Code