Two things a contributor could otherwise only find by tripping over them — and the first of them is new as of today.
main is protected. A ruleset now requires a pull request whose build check has passed before the merge, and blocks force-push and deletion. No approving review is required, and deliberately so: requiring one would lock a solo maintainer out of their own repository rather than protect anything.
A new user-visible string is work in nine catalogues. A missing key renders its English source instead of failing, so the omission is invisible from here and immediately obvious to anyone reading that language. Points at the checks, and at CLAUDE.md for the plural-key trap rather than repeating it.
Docs only — no code, no strings, no catalogue changes.
Doubling as the first PR under the new ruleset, to confirm the build context resolves and the merge is not held for an approval nobody can give.
Two things a contributor could otherwise only find by tripping over them — and the first of them is new as of today.
**`main` is protected.** A ruleset now requires a pull request whose `build` check has passed *before* the merge, and blocks force-push and deletion. No approving review is required, and deliberately so: requiring one would lock a solo maintainer out of their own repository rather than protect anything.
**A new user-visible string is work in nine catalogues.** A missing key renders its English source instead of failing, so the omission is invisible from here and immediately obvious to anyone reading that language. Points at the checks, and at `CLAUDE.md` for the plural-key trap rather than repeating it.
Docs only — no code, no strings, no catalogue changes.
Doubling as the first PR under the new ruleset, to confirm the `build` context resolves and the merge is not held for an approval nobody can give.
**Merged** 2026-09-04 as coffey-labs/ihasmail@53a44d7d18d0
<sub>Rebuilt from: git history, session transcript.</sub>
This repo is archived. You cannot comment on issues.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Two things a contributor could otherwise only find by tripping over them — and the first of them is new as of today.
mainis protected. A ruleset now requires a pull request whosebuildcheck has passed before the merge, and blocks force-push and deletion. No approving review is required, and deliberately so: requiring one would lock a solo maintainer out of their own repository rather than protect anything.A new user-visible string is work in nine catalogues. A missing key renders its English source instead of failing, so the omission is invisible from here and immediately obvious to anyone reading that language. Points at the checks, and at
CLAUDE.mdfor the plural-key trap rather than repeating it.Docs only — no code, no strings, no catalogue changes.
Doubling as the first PR under the new ruleset, to confirm the
buildcontext resolves and the merge is not held for an approval nobody can give.Merged 2026-09-04 as coffey-labs/ihasmail@53a44d7d18
Rebuilt from: git history, session transcript.