File tree Expand file tree Collapse file tree 3 files changed +29
-1
lines changed Expand file tree Collapse file tree 3 files changed +29
-1
lines changed Original file line number Diff line number Diff line change 83
83
Configuration
84
84
==============
85
85
86
- You can create in your project folder a filled called :code: `.cz `, :code: `.cz.cfg ` or in your :code: `setup.cfg `
86
+ You can create in your project folder a file called :code: `.cz `, :code: `.cz.cfg ` or in your :code: `setup.cfg `
87
87
or if you want to configure the global default in your user's home folder a :code: `.cz ` file
88
88
with the following information:
89
89
Original file line number Diff line number Diff line change
1
+ import os
1
2
from commitizen .cz .cz_base import BaseCommitizen
2
3
3
4
@@ -116,3 +117,10 @@ def schema(self):
116
117
'<body>\n '
117
118
'<BLANK LINE>\n '
118
119
'<footer>' )
120
+
121
+ def info (self ):
122
+ dir_path = os .path .dirname (os .path .realpath (__file__ ))
123
+ filepath = os .path .join (dir_path , 'cz_angular_info.txt' )
124
+ with open (filepath , 'r' ) as f :
125
+ content = f .read ()
126
+ return content
Original file line number Diff line number Diff line change
1
+ Commit Message Format
2
+
3
+ Each commit message consists of a header, a body and a footer. The header has a special format that
4
+ includes a type, a scope and a subject:
5
+
6
+ <type>(<scope>): <subject>
7
+ <BLANK LINE>
8
+ <body>
9
+ <BLANK LINE>
10
+ <footer>
11
+
12
+ The header is mandatory and the scope of the header is optional.
13
+
14
+ Any line of the commit message cannot be longer 100 characters! This allows the message to be easier
15
+ to read on GitHub as well as in various git tools.
16
+
17
+ Footer should contain a closing reference to an issue if any.
18
+
19
+ This leads to more readable messages that are easy to follow when looking through the project history.
20
+ But also, the git commit messages can be used to generate the changelog.
You can’t perform that action at this time.
0 commit comments