From e043974c44e517bcab85452bb5b7631f240a2c99 Mon Sep 17 00:00:00 2001 From: Matysh Date: Thu, 13 Aug 2026 12:11:04 +0300 Subject: [PATCH] docs: standing permission to merge a reviewed branch into dev Without it S8-merged would be a lie: the label asserts the code is in dev, while the branch-only push leaves it on the task branch. What lands is what the reviewer just accepted, and dev is allowed to carry unreviewed code anyway, so the merge adds no risk the branch did not already carry. Issue: #114 User-Visible: no --- AGENTS.md | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 2c21ee04..16667914 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -120,8 +120,15 @@ in CI and can only read what is on the remote — an unpushed spec or commit mea the review either stalls or judges the wrong tree. Pushing a task branch publishes nothing to users and does not touch the integration branch, so it needs no command. -Everything else still requires the owner's explicit command: pushing `dev` or -`main`, merging a task branch, creating tags, publishing betas and releases. +**Standing permission: after a green code review, merge the task branch into `dev` +and push `dev`.** Without it `S8-merged` would be a lie — the label asserts the code +is in `dev`. What lands is what the reviewer just accepted, and `dev` is allowed to +carry unreviewed code anyway, so the merge adds no risk the branch did not already +carry. Rebase the task branch onto `dev` first so history stays linear; the commit +is unpublished at that point, so this is not a rewrite of published history. + +Everything else still requires the owner's explicit command: pushing `main`, +creating tags, publishing betas and releases, closing issues. ## Two-agent workflow