Getting Started
Learn our commit convention
2 min read
ā¢274 wordsWe like to have a clean project history. Our commits convention is inspired by Conventional Commits but customized with gitmoji to make it more visual and fun.
Structure
The commit message should be structured as follows and in lowercase:
<gitmoji> <type> <description> [(#<issue number>)]
[optional body]
[optional footer(s)]
Example
š update documentation contributors
- Add @jerembdn as a contributor
- Add @younesbessa as a contributor
Co-authored-by: Younes Bessa <younes@onruntime.com>
Most of the time, a simple one-liner is enough:
š update documentation contributors
Types
We use the following commit types:
| Type | Description |
|---|---|
add | Add a new feature |
fix | Fix a bug |
improve | Improve something |
update | Update something |
remove | Remove something |
refactor | Refactor something |
rename | Rename something |
move | Move a file or folder |
upgrade | Upgrade dependencies |
downgrade | Downgrade dependencies |
Description
Write descriptions in imperative mood and lowercase:
# Good
š update documentation contributors
# Bad
š updated documentation contributors
# Bad
š Update documentation contributors
Issue Number
Link commits to issues by adding the issue number:
š update documentation contributors (#123)
Body
Use the body for context and motivation:
š update documentation contributors
- Add @jerembdn as a contributor
- Add @younesbessa as a contributor
Co-authored-by: Younes Bessa <younes@onruntime.com>
One Commit, One Purpose
Each commit should represent a single logical change. Don't mix unrelated changes.
Last updated on 12/31/2025