Require rebase after creating feature branch

Merge pull request 'feat: add strategy/playbook Pydantic models (issue #79 )' (#99 ) from feature/issue-79-strategy-models into main
2026-02-08 16:03:41 +09:00 · 2026-02-08 02:19:48 +09:00
1 changed files with 1 additions and 0 deletions
--- a/docs/workflow.md
+++ b/docs/workflow.md
@@ -6,6 +6,7 @@
 1. **Create Gitea Issue First** — All features, bug fixes, and policy changes require a Gitea issue before any code is written
 2. **Create Feature Branch** — Branch from `main` using format `feature/issue-{N}-{short-description}`
   - After creating the branch, run `git pull origin main` and rebase to ensure the branch is up to date
 3. **Implement Changes** — Write code, tests, and documentation on the feature branch
 4. **Create Pull Request** — Submit PR to `main` branch referencing the issue number
 5. **Review & Merge** — After approval, merge via PR (squash or merge commit)
Author	SHA1	Message	Date
agentson	7370220497	Require rebase after creating feature branch Some checks failed CI / test (pull_request) Has been cancelled Details	2026-02-08 16:03:41 +09:00
agentson	c43660a58c	Merge pull request 'feat: add strategy/playbook Pydantic models (issue #79 )' (#99 ) from feature/issue-79-strategy-models into main Some checks failed CI / test (push) Has been cancelled Details	2026-02-08 02:19:48 +09:00