Lazygit & Conventional Commits Cheat Sheet (DRAFT) by Hezart

<ty­pe>­[op­tional scope]: <de­scr­ipt­ion>

[optional body]

[optional footer(s)]

--- Options ---

fix: patches a bug in your codebase (this correlates with PATCH in Semantic Versio­ning).
feat: introduces a new feature to the codebase (this correlates with MINOR in Semantic Versio­ning).
BREAKING CHANGE: BREAKING CHANGE:, or appends a ! after the type/s­cope, introduces a breaking API change (corre­lating with MAJOR in Semantic Versio­ning). A BREAKING CHANGE can be part of commits of any type.
Others (eg: build, docs, refactor, test)

-- Examples --

feat: allow provided config object to extend other configs

BREAKING CHANGE:

extends

key in config file is now used for extending other config files

------­---­---­---­---­---­-----

feat(a­pi)!: send an email to the customer when a product is shipped

------­---­---­---­---­-------

Move between windows: Arrows or Numbers or TAB
Keybin­dings: ?
Cancel: esc
Quit: q
c: commit
p: push
[1] Status

[2] Files
space: toggle staged­/un­stanged
d: delete a file

[3] Local Branches

n: new branch


[4] Commits
scroll using PgUp/PgDn (might be changed)

[5] Stash