Skip to content

chore(git-standards): forbid emoji in commits and PR titles #266

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
JacobPEvans merged 2 commits into from
Apr 29, 2026
Merged

chore(git-standards): forbid emoji in commits and PR titles #266

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f09f571
chore(git-standards): forbid emoji in commits and PR titles
JacobPEvans Apr 29, 2026
b422698
fix(git-standards): clarify emoji-ban scope and conventional-commit p…
JacobPEvans Apr 29, 2026
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
1 change: 1 addition & 0 deletions git-standards/skills/git-workflow-standards/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,6 +48,7 @@ worktrees with uncommitted changes are NEVER stale. Use `git worktree remove` (n
- Long-running branches: rebase from main weekly
- Before PRs: ensure branch is on latest main
- Never branch from feature branches — always from main
- Commit messages: conventional-commit prefixes only, no emoji (see `pr-standards`)
Comment thread
JacobPEvans marked this conversation as resolved.

| Method | When |
| --- | --- |
Expand Down
9 changes: 9 additions & 0 deletions git-standards/skills/pr-standards/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,6 +64,15 @@ for feedback. Just resolve the thread.
Exception: explicit requests like
`@gemini-code-assist review the security implications of this change`.

## Commit, PR Title & PR Description Style

No emoji or gitmoji in commit messages, PR titles, PR descriptions, or
release notes. Conventional-commit prefixes (`feat:`, `fix:`, `chore:`,
`docs:`, etc.) are required at the start of commit subjects and PR titles
only — descriptions and release notes are plain prose.
Applies to all PRs — human, AI-assisted, and bot-authored automated fixes.
No `🤖`, no `✨`, no `🐛`. The `type(scope):` prefix carries the signal.
Comment thread
JacobPEvans marked this conversation as resolved.

## GitHub Issue Standards

### Title Prefixes
Expand Down
Loading