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 
Co-authored-by: AstroSteveo <34114851+AstroSteveo@users.noreply.github.com>
This commit is contained in:
copilot-swe-agent[bot] 2025-09-24 01:39:15 +00:00
parent ed53d053fb
commit 7e7675e447
1 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -40,3 +40,12 @@ 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 or issue you are working on.
* [ ] Use descriptive branch names following the convention: `feature/description`, `fix/description`, or `docs/description`.
* [ ] Never commit directly to the `main` branch.
* [ ] Always open a pull request for code changes, even for small updates.
* [ ] Ensure your branch is up to date with `main` before opening a pull request.
* [ ] Delete the branch after the pull request is merged.