IoTBay/.gitmessage at main · salieri009/IoTBay · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
# <type>(<scope>): <subject>
#
# <body>
#
# <footer>

# Type: Must be one of the following:
#   feat:     A new feature
#   fix:      A bug fix
#   docs:     Documentation only changes
#   style:    Changes that do not affect the meaning of the code
#   refactor: A code change that neither fixes a bug nor adds a feature
#   perf:     A code change that improves performance
#   test:     Adding missing tests or correcting existing tests
#   chore:    Changes to the build process or auxiliary tools
#   ci:       Changes to CI configuration files and scripts

# Scope: Optional, can be anything specifying the scope of the commit
#   Examples: backend, frontend, database, auth, cart, checkout, admin, etc.

# Subject: Brief description of the change (max 50 chars)
#   - Use imperative, present tense: "change" not "changed" nor "changes"
#   - Don't capitalize first letter
#   - No dot (.) at the end

# Body: Optional, detailed explanation (wrap at 72 chars)
#   - Use imperative, present tense
#   - Explain what and why vs. how
#   - Can include multiple paragraphs

# Footer: Optional
#   - Reference issue numbers: Closes #123, Fixes #456
#   - Breaking changes: BREAKING CHANGE: description

# Examples:
#   feat(auth): add password reset functionality
#   fix(cart): resolve quantity update issue
#   docs(api): update endpoint documentation
#   refactor(backend): migrate UserDAO to use DIContainer
#   style(frontend): format code with prettier
#   test(service): add unit tests for UserService
#   chore(build): update Maven dependencies
#   ci(github): add TypeScript compilation workflow