Getting Started

Learn our commit convention

2 min read
•274 words

We 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:

TypeDescription
addAdd a new feature
fixFix a bug
improveImprove something
updateUpdate something
removeRemove something
refactorRefactor something
renameRename something
moveMove a file or folder
upgradeUpgrade dependencies
downgradeDowngrade 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