From 0ed43b892373818faea1c6e9a86b9fdba5a2eb3b Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Wed, 24 Sep 2025 01:25:16 +0000 Subject: [PATCH 1/3] Initial plan From ed53d053fb5d496b82ce19b9ae030f01241d1008 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Wed, 24 Sep 2025 01:38:00 +0000 Subject: [PATCH 2/3] Initial analysis: Understanding repository structure and current state Co-authored-by: AstroSteveo <34114851+AstroSteveo@users.noreply.github.com> --- .vscode/settings.json | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/.vscode/settings.json b/.vscode/settings.json index c01085e..95e8122 100644 --- a/.vscode/settings.json +++ b/.vscode/settings.json @@ -1,11 +1,14 @@ { "chat.modeFilesLocations": { - "chatmodes": true + "chatmodes": true, + ".github/chatmodes": true }, "chat.promptFilesLocations": { - "prompts": true + "prompts": true, + ".github/prompts": true }, "chat.instructionsFilesLocations": { - "instructions": true + "instructions": true, + ".github/instructions": true } -} +} \ No newline at end of file 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 3/3] 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. +