nessar/vac-optimizer
1
0 Fork 0
Code Issues 6 Pull Requests 2 Packages Projects 1 Releases Wiki Activity

docs: document GitFlow rules for agents

Browse Source
This commit is contained in:
nessar committed 2026-10-08 08:56:00 +02:00
1 parent 964abd3546
commit 749348ec0d
1 file changed
+11
Download Patch File Download Diff File Expand all files Collapse all files
AGENTS.md
+11
View File
@@ -11,3 +11,14 @@ Use the default canonical labels: `needs-triage`, `needs-info`, `ready-for-agent
### Domain docs
This is a single-context repo using root `CONTEXT.md` and `docs/adr/`. See `docs/agents/domain.md`.
## GitFlow
- `develop` is the default integration branch; `main` contains releases. Start `feature/*` branches from the current `origin/develop` and target their MRs to `develop`.
- Rebase working branches onto the latest `origin/develop` before opening or merging an MR. If `develop` advances, rebase and rerun the MR pipeline before merging.
- Integrate through MRs with successful pipelines and Maintainer-only merges. Use merge commits (`--no-ff`) with squashing disabled. Direct and forced pushes to `main` and `develop` are forbidden.
- Use Conventional Commits for new commits and MR titles.
- Create `release/X.Y.Z` from `develop` and `hotfix/X.Y.Z` from `main`. Only `release/*` and `hotfix/*` MRs target `main`. Merge each release or hotfix into both `main` and `develop`, keeping its branch until both MRs are merged.
- Use merges and back-merges for releases and hotfixes. Never rebase `main`, `develop`, or a frozen release branch.
Before preparing a release or hotfix, creating a tag, or changing image publication, read [GitFlow and releases](README.md#gitflow-and-releases) for package versions, explicit stable tags, and image promotion.