From d8933062ab649a9ca108aac616bc297b9f42e511 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=ED=95=9C=EC=84=9D=ED=9D=AC/=EC=B1=85=EC=9E=84=EC=97=B0?= =?UTF-8?q?=EA=B5=AC=EC=9B=90/SW=20Platform=28=EC=97=B0=29Advanced=20OS=20?= =?UTF-8?q?Task?= Date: Fri, 4 Sep 2026 10:59:52 +0900 Subject: [PATCH] docs(copilot): align workflow with develop_1.0 [#38] --- .github/copilot-instructions.md | 21 ++++++++++++++------- 1 file changed, 14 insertions(+), 7 deletions(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index 096d5db..e5603c9 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -92,15 +92,22 @@ descriptions into this file. Use the document that owns the information. ## GitHub workflow -- The current default branch is `main`. Verify the current remote state before - creating a branch. +- `develop_1.0` is the default branch for ongoing development and integration. + Verify the current remote state before creating a branch or pull request. +- `main` is reserved for release-qualified delivery. - For non-trivial work, create or update a GitHub Issue and link the change to it. Follow the existing issue titles `[FEATURE]`, `[TASK]`, and `[BUG]`. +- Create one short-lived topic branch for each independent non-trivial change. + These branches isolate Issue work and provide focused review and CI; delete + them after merging. - Use a branch name in the form `/-`. Common types are `feat`, `fix`, `refactor`, `docs`, `test`, and `chore`. - Use the repository's conventional commit format and include the Issue - number, for example `docs(workflow): update Copilot guidance [#36]`. -- Open a Pull Request targeting `main`, include `Closes #` when - the PR completes the Issue, and describe the validation performed. -- Do not push directly to `main`, force-push, or merge a Pull Request without - the user's explicit request and the required project review. \ No newline at end of file + number, for example `docs(copilot): align workflow with develop_1.0 [#38]`. +- Open implementation pull requests from the topic branch to `develop_1.0`. + Include `Closes #` when the implementation PR completes the + Issue, and describe the validation performed. +- Promote selected release-qualified changes from `develop_1.0` to `main` + through a reviewed release pull request. +- Do not push directly to `develop_1.0` or `main`, force-push, or merge a pull + request without the user's explicit request and the required project review. \ No newline at end of file