8000 feat: info command for angular · ranshamay/commitizen@3a8a451 · GitHub
[go: up one dir, main page]

Skip to content

Commit 3a8a451

Browse files
committed
feat: info command for angular
1 parent b8faaec commit 3a8a451

File tree

3 files changed

+29
-1
lines changed

3 files changed

+29
-1
lines changed

README.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -83,7 +83,7 @@ Help
8383
Configuration
8484
==============
8585

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`
8787
or if you want to configure the global default in your user's home folder a :code:`.cz` file
8888
with the following information:
8989

commitizen/cz/cz_angular.py

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,4 @@
1+
import os
12
from commitizen.cz.cz_base import BaseCommitizen
23

34

@@ -116,3 +117,10 @@ def schema(self):
116117
'<body>\n'
117118
'<BLANK LINE>\n'
118119
'<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

commitizen/cz/cz_angular_info.txt

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
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.

0 commit comments

Comments
 (0)
0