Skip to content

docs(claude): add critical rule to never commit directly to main #143

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
CalvinAllen merged 1 commit into from
Dec 14, 2025
Merged

docs(claude): add critical rule to never commit directly to main #143

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 10 additions & 9 deletions .claude/CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,15 +17,16 @@ Guidance for Claude Code when working with the dtvem codebase.

**These rules override all other instructions:**

1. **Follow the styleguide** - All code must comply with `GO_STYLEGUIDE.md`
2. **Write tests** - All new/refactored code requires comprehensive unit tests
3. **Cross-platform** - All features must work on Windows, macOS, and Linux
4. **Conventional commits** - Format: `type(scope): description`
5. **GitHub Issues for TODOs** - Use `gh` CLI to manage issues, no local TODO files. Use conventional commit format for issue titles
6. **Pull Requests** - Use the conventional commit format for PR titles as you do for commits
7. **Run validation before commits** - Run `npm run check` (format, lint, test) before committing and pushing
8. **Working an issue** - When working an issue, always create a new branch from an updated main branch
9. **Branch Names** - Always use the conventional commit `type` from the issue title as the first prefix, and the `scope` as the second, then a very short description, example `feat/ci/integration-tests`
1. **NEVER commit directly to main** - Always create a feature branch and submit a pull request. No exceptions.
2. **Follow the styleguide** - All code must comply with `GO_STYLEGUIDE.md`
3. **Write tests** - All new/refactored code requires comprehensive unit tests
4. **Cross-platform** - All features must work on Windows, macOS, and Linux
5. **Conventional commits** - Format: `type(scope): description`
6. **GitHub Issues for TODOs** - Use `gh` CLI to manage issues, no local TODO files. Use conventional commit format for issue titles
7. **Pull Requests** - Use the conventional commit format for PR titles as you do for commits
8. **Run validation before commits** - Run `npm run check` (format, lint, test) before committing and pushing
9. **Working an issue** - When working an issue, always create a new branch from an updated main branch
10. **Branch Names** - Always use the conventional commit `type` from the issue title as the first prefix, and the `scope` as the second, then a very short description, example `feat/ci/integration-tests`
---

## Quick Reference
Expand Down