From 1ae455ba1a50bb60c43a8afc729478b23142d256 Mon Sep 17 00:00:00 2001 From: minixalpha Date: Sat, 22 Aug 2026 21:36:57 +0800 Subject: [PATCH] docs: require pull requests for non-release changes --- AGENTS.md | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index a97b701..a1efeed 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -52,6 +52,28 @@ the English version is in sync, even when it has already been updated. ## Commits & PRs +### Branch and pull request workflow + +All non-release changes MUST be made on a dedicated branch and merged into +`main` through a GitHub pull request. + +- Before modifying repository files, agents MUST verify that the current branch + is not `main`. If it is `main`, create or switch to a dedicated branch first. +- Agents MUST NOT commit directly to `main` or push non-release commits to + `origin/main`. +- Open a pull request targeting `main`, and use the `land-pr` skill to merge it. + Do not merge without the skill's mandatory maintainer confirmation. +- If work was accidentally started on `main`, move the changes to a dedicated + branch before committing or pushing them. + +The sole exception is the release workflow in `.agents/skills/release/SKILL.md`. +Only when the maintainer explicitly requests a release may that skill commit and +push its release-only changes directly to `main`, and only after its mandatory +confirmation gate. Documentation, chores, hotfixes, and all other work still +require a branch and pull request. + +### Commit and PR title format + All agents working in this repo MUST follow [Conventional Commits 1.0.0](https://www.conventionalcommits.org/en/v1.0.0/) for **commit messages** and **PR titles** (squash-merge often uses the PR