Skip to content

docs: track required-CI branch protection follow-up #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
DCCA merged 1 commit into from
Jun 22, 2026
+5 −0
Merged

docs: track required-CI branch protection follow-up #7

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .docs/todo/next-improvements.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 `<all_urls>` 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/`)

Expand Down
Loading