Dashboard › craft › Craft PR workflow: branch/cherry-pick/n…
019f8997-6822-757e-ac6f-edcfa32270b8| Project | Hits | Last recalled |
|---|---|---|
| opencode-lore | 2 | 28d ago |
| Code | 1 | 2026-07-01 |
Branch naming: {user}/{type}/{description}. From a feature-branch worktree, create fix branches off master: git checkout -b fix/name --track origin/master, then git cherry-pick <commit>. Commit titles follow conventional commits: fix:, feat:, refactor:, meta:, docs:. When adversarial-review fixes surface as uncommitted working-tree changes on top of a NOT-YET-PUSHED commit, amend them in (git commit --amend) to keep history coherent. Once a branch is already pushed and under active review (e.g. Bugbot/reviewers have commented on specific lines), push follow-up fixes as a NEW commit instead of amending — amending would orphan/hide the reviewed diff and break comment threading (done in PR #848, commit 42d17f0 on top of already-pushed 4e2d8f4). Attach plans as git notes (git notes add -m ..., push via git push origin refs/notes/commits). Create draft PRs with gh pr create --draft.