Skip to content

feat: allow uppercase usage in commit for acronyms #15

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

Open
Romathi wants to merge 1 commit into
base: main
Choose a base branch
from
Open

feat: allow uppercase usage in commit for acronyms #15

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
8 changes: 8 additions & 0 deletions docs/09-commits.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,6 +42,14 @@ A commit does not have uppercase, no dot (.) at the end, and no trailing whitesp
be written between brackets and preceded by a hash (#).
Any commit not following this convention will be rejected.

The only exception is when you use acronyms or code names, which should be written in uppercase. For example:

```
chore(submodules) fix submodules URLs

feat: add new UI for the project dashboard [#123456]
```

## Types

The main types you should use are listed below. As developer, you'll mostly use the following: `feat`, `fix`, `release`.
Expand Down