How to commit your codes

This section outlines some common settings we use in our projects when committing code. By parsing commits, we can catch bugs early, tag features, review code more effectively, and maintain a clean and well-organized commit history!

List of commit command

No	Preset	Description	Example
1	docs	Documentation only changes	docs: add button document
2	feature	Add new feature	feature: add button
3	fix	Fix bugs	fix: fix button color
4	fixme	Mark a bug to fix	fixme: update button color
5	performance	Improve performance of some code	performance: change search array method
6	revert	Reverts a previous commit	reverse: reverse commit 'abc'
7	style	Changes that do not affect the meaning of the code(white-space, formatting, missing semi-colons, etc)	style: change page layout
8	test	Adding missing tests or correcting existing tests	test: add test find all function
9	todo	Mark todo work, add tags TODO	todo: add test find all function
10	update	Small update	update: add test find all function