Commit Rules

1. COMMIT CODE AFTER TASK HAS BEEN DONE, BEFORE START NEW TASKS

Follow to make Weekly Report easier to write (from Ms. Nguyen Requirement)

git add -u (recommended)

git add /modules/submodules (recommended)

git add * (NOT RECOMMENDED)

git add . (NOT RECOMMENDED)

2. Syntax

<type>[optional scope]: <short description>

Type	Ý nghĩa
feat	Add feature
fix	Fix bug
docs	Change document
style	Change code format
refactor	Update code but not change the feature (clean code)
test	Update or change Unit Test
chore	Jobs not related to code (build, deploy,...)
perf	Optimize performance
ci	Change CI/CD Configuration
build	Change system configuration (maven, gradle,...)

3. Example

feat(user): add registration feature with email verification

fix(book): correct genre update logic when changing book info

docs: update README with setup instructions

style: reformat code using prettier

refactor(auth): simplify token validation logic

test(book): add test for updateBook genres logic

chore: upgrade Spring Boot to 3.2.0

Minikube

minikube start --nodes=1 --cpus=4 --memory=2048 --disk-size=5g --driver=docker