chore(ci): remove dormant push-email notification workflow - #86
Conversation
Standing estate directive limits push-email to the three defensive-lab repos (007, robodog-defensive-systems-lab, defensive-multiplicity). Tangle is not among them. The workflow was already disabled_manually and skipped on every run, so removal is a no-op for CI behaviour. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
6aac66e to
79f3d5b
Compare
|
Note Automatic reviews are paused because your trial's included automatic processing has been used for this period. Upgrade now, or comment "Gitar review" to run a review anytime. Code Review ✅ ApprovedRemoves the dormant push-email notification workflow in accordance with the defensive-lab roster directive. No issues found.
OptionsDisplay: compact → Showing less information. Comment with these commands to change the behavior for this request:
Was this helpful? React with 👍 / 👎 | Gitar |
|
|
![gitar-bot[bot]](https://avatars.githubusercontent.com/in/827041?s=60&v=4){kind=small}
1 participant
Removes
.github/workflows/push-email-notify.yml.Per the standing estate directive, push-email notification is retained only on the three defensive-lab repos (
007,robodog-defensive-systems-lab,defensive-multiplicity). Tangle is not one of them.The workflow was already
disabled_manuallyand skipped on every run, so this is a no-op for CI behaviour — it just removes a dormant, secret-consuming workflow from the roster.Note:
Dogfood Gateis currently red on all branches for an unrelated, pre-existing reason —hyperpolymath/a2ml-validate-actionandhyperpolymath/k9-validate-actionnow resolve as "repository not found" to the Actions runner (they passed on 2026-07-23). Seedev-notes/tangle-sitrep-2026-07-27.md.🤖 Generated with Claude Code