2
2
Commitizen
3
3
=============
4
4
5
- Python 3 command line utility to standardize commit messages and bump version
5
+ Python 3 command- line utility to standardize commit messages and bump version
6
6
7
7
8
8
.. image :: https://github.com/Woile/commitizen/workflows/Python%20package/badge.svg
@@ -43,13 +43,13 @@ About
43
43
44
44
Commitizen is a tool designed for teams.
45
45
46
- Its main purpose is to define a standard way of commiting rules
46
+ Its main purpose is to define a standard way of committing rules
47
47
and communicating it (using the cli provided by commitizen).
48
48
49
- The reasoning behind it is that is easier to read, and enforces writing
49
+ The reasoning behind it is that it is easier to read, and enforces writing
50
50
descriptive commits.
51
51
52
- Besides that, having a convention on your commits, makes it possible to
52
+ Besides that, having a convention on your commits makes it possible to
53
53
parse them and use them for something else, like generating automatically
54
54
the version or a changelog.
55
55
@@ -75,7 +75,7 @@ Installation
75
75
Features
76
76
========
77
77
78
- - Command line utility to create commits with your rules. Defaults: `conventional commits `_
78
+ - Command- line utility to create commits with your rules. Defaults: `conventional commits `_
79
79
- Display information about your commit rules (commands: schema, example, info)
80
80
- Bump version automatically using semantic verisoning based on the commits. `Read More <./docs/bump.md >`_
81
81
- Generate a changelog using "Keep a changelog" (Planned feature)
@@ -102,7 +102,7 @@ This is an example of how the git messages history would look like:
102
102
docs(README): added about, installation, creating, etc
103
103
feat(config): new loads from ~/.cz and working project .cz .cz.cfg and setup.cfg
104
104
105
- And then using ``cz bump `` you can change the version of your project
105
+ And then, by using ``cz bump `` , you can change the version of your project.
106
106
107
107
``feat `` to ``MINOR ``
108
108
``fix `` to ``PATCH ``
@@ -111,7 +111,7 @@ And then using ``cz bump`` you can change the version of your project
111
111
Commitizens
112
112
===========
113
113
114
- These are the available commiting styles by default:
114
+ These are the available committing styles by default:
115
115
116
116
* cz_conventional_commits: `conventional commits `_
117
117
* cz_jira: `jira smart commits <https://confluence.atlassian.com/fisheye/using-smart-commits-298976812.html >`_
@@ -156,18 +156,23 @@ Usage
156
156
optional arguments:
157
157
-h, --help show this help message and exit
158
158
--debug use debug mode
159
- -n NAME, --name NAME use the given commitizen
159
+ -n NAME, --name NAME use the given commitizen (default:
160
+ cz_conventional_commits)
160
161
--version get the version of the installed commitizen
161
162
162
163
commands:
163
- {ls,commit,c,example,info,schema,bump,check}
164
+ {ls,commit,c,example,info,schema,bump,version, check,init }
164
165
ls show available commitizens
165
166
commit (c) create new commit
166
167
example show commit example
167
168
info show information about the cz
168
169
schema show commit schema
169
170
bump bump semantic version based on the git log
170
- check enforce the project to always use conventional commits
171
+ version get the version of the installed commitizen or the
172
+ current project (default: installed commitizen)
173
+ check validates that a commit message matches the commitizen
174
+ schema
175
+ init init commitizen configuration
171
176
172
177
Contributing
173
178
============
0 commit comments