Skip to content

Instantly share code, notes, and snippets.

View CheeseCake87's full-sized avatar
🐝
Oh look, a bee.

David CheeseCake87

🐝
Oh look, a bee.
  • Scotland
  • 23:37 (UTC +01:00)
View GitHub Profile
@qoomon
qoomon / conventional-commits-cheatsheet.md
Last active July 24, 2024 17:44
Conventional Commits Cheatsheet

Conventional Commit Messages

See how a minor change to your commit message style can make a difference.

Tip

Have a look at git-conventional-commits , a CLI util to ensure these conventions, determine version and generate changelogs

Commit Message Formats

Default

@robertpainsi
robertpainsi / commit-message-guidelines.md
Last active July 17, 2024 12:55
Commit message guidelines

Commit Message Guidelines

Short (72 chars or less) summary

More detailed explanatory text. Wrap it to 72 characters. The blank
line separating the summary from the body is critical (unless you omit
the body entirely).

Write your commit message in the imperative: "Fix bug" and not "Fixed
bug" or "Fixes bug." This convention matches up with commit messages