Skip to content

docs: clarify branch confirmation before commit #683

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
BobDu merged 1 commit into from
Jan 14, 2026
Merged

docs: clarify branch confirmation before commit #683

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
2 changes: 1 addition & 1 deletion AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@
## Commit & Pull Request Guidelines
- Use Conventional Commits (e.g., `feat: add user settings`).
- Always work on a feature branch; do not commit directly to `main`.
- Create or switch to a feature branch before any changes (e.g., `git checkout -b feature/my-change`).
- Create or switch to a feature branch before any changes and always confirm the current branch before committing (e.g., `git checkout -b feature/my-change`).
- New features target the `feature` branch; other changes target `main`.
- PRs should include a clear description, link related issues, and note any UI changes with screenshots.
- Commit with signed-off and signed commits: `git commit -s -S -m "feat: ..."`.
Expand Down