-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy path.gitmessage
More file actions
43 lines (38 loc) · 1.31 KB
/
.gitmessage
File metadata and controls
43 lines (38 loc) · 1.31 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
35
36
37
38
39
40
41
42
43
# <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 one of the following:
# - setup: Main setup script changes
# - dotfiles: Dotfile configurations
# - homebrew: Brewfile and package management
# - scripts: Component scripts in scripts/
# - docs: Documentation files
# - tests: Test suite changes
# - vscode: VS Code configurations
# - zsh: Shell configuration modules
# Subject should be:
# - Written in the imperative mood
# - Not capitalized
# - No period at the end
# - Max 50 characters
# Body should:
# - Explain what and why vs. how
# - Wrap at 72 characters
# - Can use multiple paragraphs
# Footer should contain:
# - Breaking changes: BREAKING CHANGE: description
# - Issue references: Closes #123, Fixes #456