-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy path.gitmessage
95 lines (70 loc) · 2.28 KB
/
.gitmessage
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
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
# <type>(<scope>): <description>
#
# Guidelines for the header:
# - <type>: Commit type, e.g., feat, fix, docs, chore, refactor, deps, test, security, etc.
# - <scope>: Optional. The specific module, feature, or area affected.
# - <description>: A short, imperative summary of the change.
#
# Example: feat(auth): add OAuth login support
<type>(<scope>): <description>
# Detailed description:
# - Explain the change in more depth if necessary.
# - Provide additional context or motivations.
<detailed description>
# Affected files:
# - Use one or more of these sections to list affected files.
# - List filenames and briefly describe their role in the change.
#
# [FILES ADDED] -> Newly created files.
# [FILES MODIFIED] -> Files that were updated.
# [FILES REMOVED] -> Files that were deleted.
[FILES ADDED]
- <list of files>
[FILES MODIFIED]
- <list of files>
[FILES REMOVED]
- <list of files>
# Dependencies:
# - Document any changes to project dependencies.
# - Use these sections for newly added, updated, or removed dependencies.
#
# [DEPENDENCIES ADDED] -> New dependencies.
# [DEPENDENCIES UPDATED]-> Updated dependencies.
# [DEPENDENCIES REMOVED]-> Removed dependencies.
[DEPENDENCIES ADDED]
- <list of dependencies>
[DEPENDENCIES UPDATED]
- <list of dependencies>
[DEPENDENCIES REMOVED]
- <list of dependencies>
# Features/Changes:
# - Summarize the new features, updates, or changes in this commit.
[FEATURES/CHANGES]
- <list of features or changes>
# Techniques:
# - Optionally document the approaches, tools, or methods used.
[TECHNIQUES]
- <details of techniques used>
# Breaking Changes:
# - Use this section for any breaking changes.
# - Provide details about what broke and how users can adapt.
[BREAKING CHANGE]
- <description of breaking change>
# Purpose:
# - Explain why this change was needed.
[PURPOSE]
- <reason for the change>
# Impact:
# - Describe the effect of the change on the project or users.
[IMPACT]
- <description of the impact>
# Issue References:
# - Use one of these keywords to reference issues resolved by this commit:
# FIXES, CLOSES, or RESOLVES.
# - Add the issue number(s).
[FIXES/CLOSES/RESOLVES]
- #<issue number>
# References:
# - Link to related documentation, code reviews, or designs.
[REFERENCES]
- <links to resources>