From 33d1c426967916d851bde10f192a18ff9e7c812c Mon Sep 17 00:00:00 2001 From: Claude Date: Mon, 22 Jun 2026 12:04:24 +0000 Subject: [PATCH] docs: track 'protect main with required CI check' follow-up MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Record the branch-protection follow-up (require the validate check + a PR before merging to main) so red changes can't land — the gate that would have caught the unformatted UI PRs. Repo-settings action requiring admin. Co-Authored-By: Claude Opus 4.8 Claude-Session: https://claude.ai/code/session_01PJ5c2e5VcKVhugy7TAzi4W --- .docs/todo/next-improvements.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/.docs/todo/next-improvements.md b/.docs/todo/next-improvements.md index e6b41c0..76ba6fd 100644 --- a/.docs/todo/next-improvements.md +++ b/.docs/todo/next-improvements.md @@ -10,6 +10,11 @@ - Show a total local-storage usage indicator (per-share size is shown today). - Evaluate moving the content script fully to on-demand injection (drop the static `` registration). See `SECURITY.md` → Known follow-up. +- **Protect `main`** (repo-settings action, needs admin): require the `validate` + status check to pass and require a PR before merging, so changes can't land on + `main` while CI is red. This gate is what would have blocked the unformatted + UI PRs (#3–#5) that broke `main`. Configure under **Settings → Branches → + Branch protection rules** (or a Ruleset) for `main`. ## Done (see `.docs/done/2026-06-20-world-class-hardening/`)