josiadmin/awesome-copilot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: add branching policy to copilot-instructions

Browse Source
This commit is contained in:
AstroSteveo 2025-09-23 20:24:56 -05:00
parent 3f6f0291f0
commit 3fa4682a72
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
.github/copilot-instructions.md vendored
View File

@ -40,3 +40,14 @@ The following instructions are only to be applied when performing a code review.
* [ ] Encourage the use of `tools`, but it's not required. * [ ] Encourage the use of `tools`, but it's not required.
* [ ] Strongly encourage the use of `model` to specify the model that the chat mode is optimised for. * [ ] Strongly encourage the use of `model` to specify the model that the chat mode is optimised for.
## Branching Policy
- Always create a new branch for each task, feature, or fix.
- Use the following naming conventions:
- `feature/<short-description>`
- `bugfix/<short-description>`
- `task/<short-description>`
- Never commit changes directly to the `main` or default branch.
- After completing changes, push the branch and open a pull request for review and merging.