touches_protected() hard-coded all of .github/ and .gitea/ on top of TIME_PROTECTED, so the engine under .github/time/ could never land without a human whatever the variable said. That is how #59 sat for three days with a reviewer Approve, green CI and eleven steward sign-offs, and why #74 needed a hand today.
Only .github/workflows/ and .gitea/workflows/ stay hard-coded: workflows remain a human's merge whatever TIME_PROTECTED says.
DEFAULT_PROTECTED is unchanged (.github/,.gitea/,deploy,infra/,.env,secret), so a repo that has not set the variable behaves exactly as before. Time ships to other repos; their defaults don't move.
This repo's TIME_PROTECTED is already set to .github/workflows/,.gitea/workflows/,deploy,infra/,.env,secret, so once this lands, card PRs under .github/time/ with a trusted Approve and green checks merge via the time bot.
Tests (check 13 area): the default still holds a PR touching .github/time/time.py; the narrowed variable lets the same PR merge; with TIME_PROTECTED=deploy a PR touching .gitea/workflows/ci.yml is still held.
CHANGELOG line under "### Added".
Same defect as Codex's write-up in #68 (comment 626); this is the implementation. Opened and, once CI is green, merged by the CEO session on the owner's explicit instruction.
`touches_protected()` hard-coded all of `.github/` and `.gitea/` on top of `TIME_PROTECTED`, so the engine under `.github/time/` could never land without a human whatever the variable said. That is how #59 sat for three days with a reviewer Approve, green CI and eleven steward sign-offs, and why #74 needed a hand today.
- Only `.github/workflows/` and `.gitea/workflows/` stay hard-coded: workflows remain a human's merge whatever `TIME_PROTECTED` says.
- `DEFAULT_PROTECTED` is unchanged (`.github/,.gitea/,deploy,infra/,.env,secret`), so a repo that has not set the variable behaves exactly as before. Time ships to other repos; their defaults don't move.
- This repo's `TIME_PROTECTED` is already set to `.github/workflows/,.gitea/workflows/,deploy,infra/,.env,secret`, so once this lands, card PRs under `.github/time/` with a trusted Approve and green checks merge via the `time` bot.
- Tests (check 13 area): the default still holds a PR touching `.github/time/time.py`; the narrowed variable lets the same PR merge; with `TIME_PROTECTED=deploy` a PR touching `.gitea/workflows/ci.yml` is still held.
- CHANGELOG line under "### Added".
Same defect as Codex's write-up in #68 (comment 626); this is the implementation. Opened and, once CI is green, merged by the CEO session on the owner's explicit instruction.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_017K4vyY3yUD3GsvoZaAtKkD
touches_protected() hard-coded all of .github/ and .gitea/ on top of TIME_PROTECTED, so the engine under .github/time/ could never land without a human whatever the variable said. Only .github/workflows/ and .gitea/workflows/ stay hard-coded; DEFAULT_PROTECTED is unchanged, so a repo that has not set the variable behaves exactly as before.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017K4vyY3yUD3GsvoZaAtKkD
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.
touches_protected()hard-coded all of.github/and.gitea/on top ofTIME_PROTECTED, so the engine under.github/time/could never land without a human whatever the variable said. That is how #59 sat for three days with a reviewer Approve, green CI and eleven steward sign-offs, and why #74 needed a hand today..github/workflows/and.gitea/workflows/stay hard-coded: workflows remain a human's merge whateverTIME_PROTECTEDsays.DEFAULT_PROTECTEDis unchanged (.github/,.gitea/,deploy,infra/,.env,secret), so a repo that has not set the variable behaves exactly as before. Time ships to other repos; their defaults don't move.TIME_PROTECTEDis already set to.github/workflows/,.gitea/workflows/,deploy,infra/,.env,secret, so once this lands, card PRs under.github/time/with a trusted Approve and green checks merge via thetimebot..github/time/time.py; the narrowed variable lets the same PR merge; withTIME_PROTECTED=deploya PR touching.gitea/workflows/ci.ymlis still held.Same defect as Codex's write-up in #68 (comment 626); this is the implementation. Opened and, once CI is green, merged by the CEO session on the owner's explicit instruction.
🤖 Generated with Claude Code
https://claude.ai/code/session_017K4vyY3yUD3GsvoZaAtKkD