From 7e7675e4475a4bf98f5144537f3f28b792ee82ff Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Wed, 24 Sep 2025 01:39:15 +0000
Subject: [PATCH] docs: add branching policy to copilot-instructions

Co-authored-by: AstroSteveo <34114851+AstroSteveo@users.noreply.github.com>
---
 .github/copilot-instructions.md | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md
index d121970..36aff72 100644
--- a/.github/copilot-instructions.md
+++ b/.github/copilot-instructions.md
@@ -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.
 * [ ] 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.
+