286
286
287
287
288
288
289
-
290
-
291
- < li class ="md-nav__item ">
292
- < a href ="../../getting_started/ " class ="md-nav__link ">
293
-
294
-
295
- < span class ="md-ellipsis ">
296
- Getting Started
297
- </ span >
298
-
299
-
300
- </ a >
301
- </ li >
302
-
303
-
304
-
305
-
306
-
307
-
308
-
309
289
310
290
311
291
318
298
319
299
320
300
321
- < input class ="md-nav__toggle md-toggle " type ="checkbox " id ="__nav_3 " checked >
301
+ < input class ="md-nav__toggle md-toggle " type ="checkbox " id ="__nav_2 " checked >
322
302
323
303
324
- < label class ="md-nav__link " for ="__nav_3 " id ="__nav_3_label " tabindex ="0 ">
304
+ < label class ="md-nav__link " for ="__nav_2 " id ="__nav_2_label " tabindex ="0 ">
325
305
326
306
327
307
< span class ="md-ellipsis ">
332
312
< span class ="md-nav__icon md-icon "> </ span >
333
313
</ label >
334
314
335
- < nav class ="md-nav " data-md-level ="1 " aria-labelledby ="__nav_3_label " aria-expanded ="true ">
336
- < label class ="md-nav__title " for ="__nav_3 ">
315
+ < nav class ="md-nav " data-md-level ="1 " aria-labelledby ="__nav_2_label " aria-expanded ="true ">
316
+ < label class ="md-nav__title " for ="__nav_2 ">
337
317
< span class ="md-nav__icon md-icon "> </ span >
338
318
Commands
339
319
</ label >
997
977
998
978
999
979
1000
- < input class ="md-nav__toggle md-toggle " type ="checkbox " id ="__nav_6 " >
980
+ < input class ="md-nav__toggle md-toggle " type ="checkbox " id ="__nav_5 " >
1001
981
1002
982
1003
- < label class ="md-nav__link " for ="__nav_6 " id ="__nav_6_label " tabindex ="0 ">
983
+ < label class ="md-nav__link " for ="__nav_5 " id ="__nav_5_label " tabindex ="0 ">
1004
984
1005
985
1006
986
< span class ="md-ellipsis ">
1011
991
< span class ="md-nav__icon md-icon "> </ span >
1012
992
</ label >
1013
993
1014
- < nav class ="md-nav " data-md-level ="1 " aria-labelledby ="__nav_6_label " aria-expanded ="false ">
1015
- < label class ="md-nav__title " for ="__nav_6 ">
994
+ < nav class ="md-nav " data-md-level ="1 " aria-labelledby ="__nav_5_label " aria-expanded ="false ">
995
+ < label class ="md-nav__title " for ="__nav_5 ">
1016
996
< span class ="md-nav__icon md-icon "> </ span >
1017
997
Tutorials
1018
998
</ label >
@@ -1774,7 +1754,7 @@ <h3 id="-changelog"><code>--changelog</code><a class="headerlink" href="#-change
1774
1754
< h3 id ="-prerelease "> < code > --prerelease</ code > < a class ="headerlink " href ="#-prerelease " title ="Permanent link "> ¶</ a > </ h3 >
1775
1755
< p > The bump is a pre-release bump, meaning that in addition to a possible version bump the new version receives a
1776
1756
pre-release segment compatible with the bump’s version scheme, where the segment consist of a < em > phase</ em > and a
1777
- non-negative number. Supported options for < code > --prerelease</ code > are the following phase names < code > alpha</ code > , < code > beta</ code > , or
1757
+ non-negative number. Supported options for < code > --prerelease</ code > are the following phase names < code > alpha</ code > , < code > beta</ code > , or
1778
1758
< code > rc</ code > (release candidate). For more details, refer to the
1779
1759
< a href ="https://packaging.python.org/en/latest/specifications/version-specifiers/#pre-releases "> Python Packaging User Guide</ a > .</ p >
1780
1760
< p > Note that as per < a href ="https://semver.org/#spec-item-9 "> semantic versioning spec</ a > </ p >
@@ -1858,7 +1838,7 @@ <h3 id="-increment-mode"><code>--increment-mode</code><a class="headerlink" href
1858
1838
</ tbody >
1859
1839
</ table >
1860
1840
< h3 id ="-check-consistency "> < code > --check-consistency</ code > < a class ="headerlink " href ="#-check-consistency " title ="Permanent link "> ¶</ a > </ h3 >
1861
- < p > Check whether the versions defined in < code > version_files</ code > and the version in commitizen
1841
+ < p > Check whether the versions defined in < code > version_files</ code > and the version in Commitizen
1862
1842
configuration are consistent before bumping version.</ p >
1863
1843
< div class ="highlight "> < pre > < span > </ span > < code > cz< span class ="w "> </ span > bump< span class ="w "> </ span > --check-consistency
1864
1844
</ code > </ pre > </ div >
@@ -1878,7 +1858,7 @@ <h3 id="-check-consistency"><code>--check-consistency</code><a class="headerlink
1878
1858
1879
1859
< span class ="n "> setup</ span > < span class ="p "> (</ span > < span class ="o "> ...</ span > < span class ="p "> ,</ span > < span class ="n "> version</ span > < span class ="o "> =</ span > < span class ="s2 "> "1.0.5"</ span > < span class ="p "> ,</ span > < span class ="o "> ...</ span > < span class ="p "> )</ span >
1880
1860
</ code > </ pre > </ div >
1881
- < p > If < code > --check-consistency</ code > is used, commitizen will check whether the current version in < code > pyproject.toml</ code >
1861
+ < p > If < code > --check-consistency</ code > is used, Commitizen will check whether the current version in < code > pyproject.toml</ code >
1882
1862
exists in all version_files and find out it does not exist in < code > setup.py</ code > and fails.
1883
1863
However, it will still update < code > pyproject.toml</ code > and < code > src/__version__.py</ code > .</ p >
1884
1864
< p > To fix it, you'll first < code > git checkout .</ code > to reset to the status before trying to bump and update
@@ -1893,9 +1873,9 @@ <h3 id="-local-version"><code>--local-version</code><a class="headerlink" href="
1893
1873
</ code > </ pre > </ div >
1894
1874
< p > If < code > --local-version</ code > is used, it will bump only the local version < code > 0.1.0</ code > and keep the public version < code > 5.3.5</ code > intact, bumping to the version < code > 5.3.5+0.2.0</ code > .</ p >
1895
1875
< h3 id ="-annotated-tag "> < code > --annotated-tag</ code > < a class ="headerlink " href ="#-annotated-tag " title ="Permanent link "> ¶</ a > </ h3 >
1896
- < p > If < code > --annotated-tag</ code > is used, commitizen will create annotated tags. Also available via configuration, in < code > pyproject.toml</ code > or < code > .cz.toml</ code > .</ p >
1876
+ < p > If < code > --annotated-tag</ code > is used, Commitizen will create annotated tags. It is also available via configuration, in < code > pyproject.toml</ code > or < code > .cz.toml</ code > .</ p >
1897
1877
< h3 id ="-annotated-tag-message "> < code > --annotated-tag-message</ code > < a class ="headerlink " href ="#-annotated-tag-message " title ="Permanent link "> ¶</ a > </ h3 >
1898
- < p > If < code > --annotated-tag-message</ code > is used, commitizen will create annotated tags with the given message.</ p >
1878
+ < p > If < code > --annotated-tag-message</ code > is used, Commitizen will create annotated tags with the given message.</ p >
1899
1879
< h3 id ="-changelog-to-stdout "> < code > --changelog-to-stdout</ code > < a class ="headerlink " href ="#-changelog-to-stdout " title ="Permanent link "> ¶</ a > </ h3 >
1900
1880
< p > If < code > --changelog-to-stdout</ code > is used, the incremental changelog generated by the bump
1901
1881
will be sent to the stdout, and any other message generated by the bump will be
@@ -2013,10 +1993,10 @@ <h3 id="-allow-no-commit"><code>--allow-no-commit</code><a class="headerlink" hr
2013
1993
cz< span class ="w "> </ span > bump< span class ="w "> </ span > --allow-no-commit< span class ="w "> </ span > < span class ="m "> 2</ span > .0.0
2014
1994
</ code > </ pre > </ div >
2015
1995
< h2 id ="avoid-raising-errors "> Avoid raising errors< a class ="headerlink " href ="#avoid-raising-errors " title ="Permanent link "> ¶</ a > </ h2 >
2016
- < p > Some situations from commitizen raise an exit code different than 0.
2017
- If the error code is different than 0, any CI or script running commitizen might be interrupted.</ p >
1996
+ < p > Some situations from Commitizen raise an exit code different from 0.
1997
+ If the error code is different from 0, any CI or script running Commitizen might be interrupted.</ p >
2018
1998
< p > If you have a special use case, where you don't want to raise one of this error codes, you can
2019
- tell commitizen to not raise them.</ p >
1999
+ tell Commitizen to not raise them.</ p >
2020
2000
< h3 id ="recommended-use-case "> Recommended use case< a class ="headerlink " href ="#recommended-use-case " title ="Permanent link "> ¶</ a > </ h3 >
2021
2001
< p > At the moment, we've identified that the most common error code to skip is</ p >
2022
2002
< table >
@@ -2038,24 +2018,24 @@ <h3 id="recommended-use-case">Recommended use case<a class="headerlink" href="#r
2038
2018
< div class ="highlight "> < pre > < span > </ span > < code > cz< span class ="w "> </ span > -nr< span class ="w "> </ span > < span class ="m "> 21</ span > < span class ="w "> </ span > bump
2039
2019
</ code > </ pre > </ div >
2040
2020
< h3 id ="easy-way "> Easy way< a class ="headerlink " href ="#easy-way " title ="Permanent link "> ¶</ a > </ h3 >
2041
- < p > Check which error code was raised by commitizen by running in the terminal</ p >
2021
+ < p > Check which error code was raised by Commitizen by running in the terminal</ p >
2042
2022
< div class ="highlight "> < pre > < span > </ span > < code > < span class ="nb "> echo</ span > < span class ="w "> </ span > < span class ="nv "> $?</ span >
2043
2023
</ code > </ pre > </ div >
2044
2024
< p > The output should be an integer like this</ p >
2045
2025
< div class ="highlight "> < pre > < span > </ span > < code > < span class ="m "> 3</ span >
2046
2026
</ code > </ pre > </ div >
2047
- < p > And then you can tell commitizen to ignore it:</ p >
2027
+ < p > And then you can tell Commitizen to ignore it:</ p >
2048
2028
< div class ="highlight "> < pre > < span > </ span > < code > cz< span class ="w "> </ span > --no-raise< span class ="w "> </ span > < span class ="m "> 3</ span >
2049
2029
</ code > </ pre > </ div >
2050
- < p > You can tell commitizen to skip more than one if needed:</ p >
2030
+ < p > You can tell Commitizen to skip more than one if needed:</ p >
2051
2031
< div class ="highlight "> < pre > < span > </ span > < code > cz< span class ="w "> </ span > --no-raise< span class ="w "> </ span > < span class ="m "> 3</ span > ,4,5
2052
2032
</ code > </ pre > </ div >
2053
2033
< h3 id ="longer-way "> Longer way< a class ="headerlink " href ="#longer-way " title ="Permanent link "> ¶</ a > </ h3 >
2054
2034
< p > Check the list of < a href ="../../exit_codes/ "> exit_codes</ a > and understand which one you have
2055
2035
to skip and why.</ p >
2056
2036
< p > Remember to document somewhere this, because you'll forget.</ p >
2057
2037
< p > For example if the system raises a < code > NoneIncrementExit</ code > error, you look it up
2058
- on the list and then you can use the exit code:</ p >
2038
+ on the list, and then you can use the exit code:</ p >
2059
2039
< div class ="highlight "> < pre > < span > </ span > < code > cz< span class ="w "> </ span > -nr< span class ="w "> </ span > < span class ="m "> 21</ span > < span class ="w "> </ span > bump
2060
2040
</ code > </ pre > </ div >
2061
2041
< h2 id ="configuration "> Configuration< a class ="headerlink " href ="#configuration " title ="Permanent link "> ¶</ a > </ h2 >
@@ -2065,7 +2045,7 @@ <h3 id="tag_format"><code>tag_format</code><a class="headerlink" href="#tag_form
2065
2045
< ul >
2066
2046
< li > < code > cz bump</ code > : Find previous release tag (exact match) and generate new tag.</ li >
2067
2047
< li > Find previous release tags in < code > cz changelog</ code > .</ li >
2068
- < li > If < code > --incremental</ code > : Using latest version found in the changelog, scan existing Git tags with 89\% similarity match.</ li >
2048
+ < li > If < code > --incremental</ code > : Using the latest version found in the changelog, scan existing Git tags with 89\% similarity match.</ li >
2069
2049
< li > < code > --rev-range</ code > is converted to Git tag names with < code > tag_format</ code > before searching Git history.</ li >
2070
2050
< li > If the < code > scm</ code > < code > version_provider</ code > is used, it uses different regexes to find the previous version tags:</ li >
2071
2051
< li > If < code > tag_format</ code > is set to < code > $version</ code > (default): < code > VersionProtocol.parser</ code > (allows < code > v</ code > prefix)</ li >
@@ -2142,7 +2122,7 @@ <h3 id="version_files"><code>version_files</code> *<a class="headerlink" href="#
2142
2122
< hr />
2143
2123
< h3 id ="bump_message "> < code > bump_message</ code > < a class ="headerlink " href ="#bump_message " title ="Permanent link "> ¶</ a > </ h3 >
2144
2124
< p > Template used to specify the commit message generated when bumping.</ p >
2145
- < p > defaults to: < code > bump: version $current_version → $new_version</ code > </ p >
2125
+ < p > Defaults to: < code > bump: version $current_version → $new_version</ code > </ p >
2146
2126
< table >
2147
2127
< thead >
2148
2128
< tr >
@@ -2169,25 +2149,25 @@ <h3 id="bump_message"><code>bump_message</code><a class="headerlink" href="#bump
2169
2149
< hr />
2170
2150
< h3 id ="update_changelog_on_bump "> < code > update_changelog_on_bump</ code > < a class ="headerlink " href ="#update_changelog_on_bump " title ="Permanent link "> ¶</ a > </ h3 >
2171
2151
< p > When set to < code > true</ code > the changelog is always updated incrementally when running < code > cz bump</ code > , so the user does not have to provide the < code > --changelog</ code > flag every time.</ p >
2172
- < p > defaults to: < code > false</ code > </ p >
2152
+ < p > Defaults to: < code > false</ code > </ p >
2173
2153
< div class ="highlight "> < pre > < span > </ span > < code > < span class ="k "> [tool.commitizen]</ span >
2174
2154
< span class ="n "> update_changelog_on_bump</ span > < span class ="w "> </ span > < span class ="o "> =</ span > < span class ="w "> </ span > < span class ="kc "> true</ span >
2175
2155
</ code > </ pre > </ div >
2176
2156
< hr />
2177
2157
< h3 id ="annotated_tag "> < code > annotated_tag</ code > < a class ="headerlink " href ="#annotated_tag " title ="Permanent link "> ¶</ a > </ h3 >
2178
- < p > When set to < code > true</ code > commitizen will create annotated tags.</ p >
2158
+ < p > When set to < code > true</ code > , Commitizen will create annotated tags.</ p >
2179
2159
< div class ="highlight "> < pre > < span > </ span > < code > < span class ="k "> [tool.commitizen]</ span >
2180
2160
< span class ="n "> annotated_tag</ span > < span class ="w "> </ span > < span class ="o "> =</ span > < span class ="w "> </ span > < span class ="kc "> true</ span >
2181
2161
</ code > </ pre > </ div >
2182
2162
< hr />
2183
2163
< h3 id ="gpg_sign "> < code > gpg_sign</ code > < a class ="headerlink " href ="#gpg_sign " title ="Permanent link "> ¶</ a > </ h3 >
2184
- < p > When set to < code > true</ code > commitizen will create gpg signed tags.</ p >
2164
+ < p > When set to < code > true</ code > , Commitizen will create gpg signed tags.</ p >
2185
2165
< div class ="highlight "> < pre > < span > </ span > < code > < span class ="k "> [tool.commitizen]</ span >
2186
2166
< span class ="n "> gpg_sign</ span > < span class ="w "> </ span > < span class ="o "> =</ span > < span class ="w "> </ span > < span class ="kc "> true</ span >
2187
2167
</ code > </ pre > </ div >
2188
2168
< hr />
2189
2169
< h3 id ="major_version_zero "> < code > major_version_zero</ code > < a class ="headerlink " href ="#major_version_zero " title ="Permanent link "> ¶</ a > </ h3 >
2190
- < p > When set to < code > true</ code > commitizen will keep the major version at zero.
2170
+ < p > When set to < code > true</ code > , Commitizen will keep the major version at zero.
2191
2171
Useful during the initial development stage of your project.</ p >
2192
2172
< p > Defaults to: < code > false</ code > </ p >
2193
2173
< div class ="highlight "> < pre > < span > </ span > < code > < span class ="k "> [tool.commitizen]</ span >
0 commit comments