Skip to content

docs(claude): agents do not merge to 2026 and do not deploy - #334

Open
ryzizub wants to merge 1 commit into
2026from
chore/agent-production-branch-rule
Open

docs(claude): agents do not merge to 2026 and do not deploy#334
ryzizub wants to merge 1 commit into
2026from
chore/agent-production-branch-rule

Conversation

@ryzizub

@ryzizub ryzizub commented Sep 6, 2026

Copy link
Copy Markdown
Member

Summary

Adds a rule section at the top of CLAUDE.md: agents never merge to 2026, never push to it, never deploy. An agent's delivery ends at branch pushed + PR opened + CI result reported.

Why

A merge into 2026 triggers the Firebase Hosting deploy, so a merge is a deploy to devfest.cz. In DEVF-54 an agent read "push it to branch so its redeployed" as merge permission and shipped /attending to production without approval (reverted in #333). The rule spells out what was implicit:

  • "push it" / "redeploy" / "ship it" / green CI are not merge permission — only an instruction naming the merge is.
  • Permission is per PR, once; it does not carry to the next PR or a follow-up fix.
  • Hand back the PR preview URL, never a production URL.

The same rule is now also in the Multica workspace context, so it reaches agents that never open this repo.

Files

  • CLAUDE.md — new section, docs only, no code touched.

A merge into `2026` triggers the Firebase Hosting deploy, so a merge is a
deploy to devfest.cz. Record that the maintainer is the only one who does it:
an agent's delivery ends at branch pushed + PR opened + CI reported, "push it"
/ "redeploy" / green CI are not merge permission, permission is per PR and does
not carry over, and the hand-off carries the PR preview URL, not a production one.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant