Require feature branches in agent instructions
This commit is contained in:
1 file changed
+12
@@ -0,0 +1,12 @@
|
|||||||
|
# Git workflow
|
||||||
|
|
||||||
|
- Create and switch to a feature branch before editing files or making commits.
|
||||||
|
- Never commit directly on `main` or `master`.
|
||||||
|
- Use descriptive branch names, such as `feat/mpd-fifo-output-monitoring`,
|
||||||
|
`fix/readme-images`, or `chore/agent-instructions`.
|
||||||
|
- Continue on an existing feature branch when working on the same task. Create a
|
||||||
|
separate branch from the target branch for unrelated work.
|
||||||
|
- If changes already exist on `main` or `master`, create a feature branch that
|
||||||
|
preserves those changes before committing them.
|
||||||
|
- Open pull requests against the target branch; do not merge or push changes
|
||||||
|
directly to `main` or `master` unless the user explicitly requests it.
|
||||||
Reference in new issue
Block a user