ci: release pull requests, and conventional-commit PR titles

Pull requests only, squash-merged, titled as conventional commits (checked); release-bot keeps a chore(release) pull request open, worked out by git-cliff, and merging it tags the release. Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-11-03 08:37:17 +00:00
1 parent f60ba346f8
commit 814b00f82b
@@ -9,4 +9,11 @@ package (`docs/pack.md`).
 - Never commit IMVU's files: tests make their product files in code (a minimal `index.xml`, fake textures).
 - Never commit secrets (catalog keys, tokens).
 - Commits: author "dhkatz <dev@t5de.dev>"; never the user's real name or email.
+- Changes reach main only through pull requests, squash-merged: the PR's title becomes the commit on main, so it must
+  be a conventional commit (`feat(api): …`, `fix(web): …`, `docs: …`; `!` before the colon for a breaking change),
+  checked by `.gitea/workflows/pull-request.yml`. Commits on the branch can be anything. Push a branch and open the
+  pull request on git.t5de.dev (web UI or API); the user merges.
+- Releases: release-bot keeps a `chore(release): vX.Y.Z` pull request open (`release.yml`, git-cliff from those
+  titles); merging it tags vX.Y.Z, which builds the image and deploys prod. Never tag by hand (v* tags are
+  release-bot's).
 - Follow `docs/products.md` exactly; change it there (in t5de-hub) first if the contract needs to change.