cal/major-domo-v2
1
0
Fork 0
Code Issues 6 Pull Requests 2 Actions Packages Projects Releases Wiki Activity

docs: clarify git branching workflow in CLAUDE.md

Browse Source 
Branch from next-release for normal work, main only for hotfixes.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Cal Corum 2026-03-02 13:42:18 -06:00
parent 858663cd27
commit c961ea0dea
1 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
CLAUDE.md
View File

@ -16,10 +16,15 @@ manticorum67/major-domo-discordapp
There is NO DASH between "discord" and "app". Not `discord-app`, not `discordapp-v2`. There is NO DASH between "discord" and "app". Not `discord-app`, not `discordapp-v2`.
### Git Workflow ### Git Workflow
NEVER commit directly to `main`. Always use feature branches: NEVER commit directly to `main` or `next-release`. Always use feature branches.
**Branch from `next-release`** for normal work targeting the next release:
```bash ```bash
git checkout -b feature/name # or fix/name git checkout -b feature/name origin/next-release # or fix/name, refactor/name
``` ```
**Branch from `main`** only for urgent hotfixes that bypass the release cycle.
PRs go to `next-release` (staging), then `next-release → main` when releasing.
### Double Emoji in Embeds ### Double Emoji in Embeds
`EmbedTemplate.success/error/warning/info/loading()` auto-add emoji prefixes. `EmbedTemplate.success/error/warning/info/loading()` auto-add emoji prefixes.