-
Notifications
You must be signed in to change notification settings - Fork 4
Home
LeNDuyA edited this page Dec 9, 2025
·
20 revisions
1. Check out the architecture and follow it
-
every branch follows this format:
type/username/task-
typecan be one of the following:-
feat- a new feature -
fix- a bug fix -
docs- documentation changes only -
style- code formatting (whitespace, indentation, etc.) -
refactor- a code refactor -
test- adding or updating tests -
chore- auxiliary tasks (dependencies, build scripts, etc.) -
build- changes to build tools or external dependencies -
ci- continuous integration configuration or script changes -
perf- performance optimizations -
revert- undoing previous changes -
merge- combining changes from different branches -
BREAKING CHANGE- denotes breaking changes (mark with!or useBREAKING CHANGE:footer)
-
-
-
every commit message follows this format:
type(topic):commit message- same
types as above -
topicis a region that the code manipulates:-
base- code-base-wide changes -
core- core module - feature:
infil,wavuetc - sub-feature:
embedetc
-
- present tense and in English
- same