-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy path.gitmessage
More file actions
34 lines (34 loc) · 1.07 KB
/
.gitmessage
File metadata and controls
34 lines (34 loc) · 1.07 KB
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
# <type>(<scope>): <subject>
#
# <body>
#
# <footer>
#
# Type should 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
# * build: Changes that affect the build system or external dependencies
# * ci: Changes to our CI configuration files and scripts
# * chore: Other changes that don't modify src or test files
# * revert: Reverts a previous commit
#
# Scope should be the package name (adk, adt-cli, cds2abap, etc.)
#
# Subject line should:
# * Use imperative mood ("Add feature" not "Added feature")
# * Not exceed 50 characters
# * Not end with a period
#
# Body should:
# * Explain what and why, not how
# * Use imperative mood
# * Wrap at 72 characters
#
# Footer should contain:
# * Breaking changes (start with "BREAKING CHANGE:")
# * Issue references (e.g., "Closes #123", "Fixes #456")