@@ -1720,15 +1720,19 @@ <h4 id="version-management">Version Management<a class="headerlink" href="#versi
1720
1720
< p > The most common command you'll use is:
1721
1721
< div class ="highlight "> < pre > < span > </ span > < code > cz< span class ="w "> </ span > bump
1722
1722
</ code > </ pre > </ div > </ p >
1723
- < p > This command:
1724
- - Bumps your project's version
1725
- - Creates a git tag
1726
- - Updates the changelog (if < code > update_changelog_on_bump</ code > is enabled)
1727
- - Updates version files</ p >
1728
- < p > You can customize:
1729
- - < a href ="https://commitizen-tools.github.io/commitizen/commands/bump/#version_files "> Version files</ a >
1730
- - < a href ="https://commitizen-tools.github.io/commitizen/commands/bump/#version_scheme "> Version scheme</ a >
1731
- - < a href ="https://commitizen-tools.github.io/commitizen/config/#version-providers "> Version provider</ a > </ p >
1723
+ < p > This command:</ p >
1724
+ < ul >
1725
+ < li > Bumps your project's version</ li >
1726
+ < li > Creates a git tag</ li >
1727
+ < li > Updates the changelog (if < code > update_changelog_on_bump</ code > is enabled)</ li >
1728
+ < li > Updates version files</ li >
1729
+ </ ul >
1730
+ < p > You can customize:</ p >
1731
+ < ul >
1732
+ < li > < a href ="https://commitizen-tools.github.io/commitizen/commands/bump/#version_files "> Version files</ a > </ li >
1733
+ < li > < a href ="https://commitizen-tools.github.io/commitizen/commands/bump/#version_scheme "> Version scheme</ a > </ li >
1734
+ < li > < a href ="https://commitizen-tools.github.io/commitizen/config/#version-providers "> Version provider</ a > </ li >
1735
+ </ ul >
1732
1736
< p > For all available options, see the < a href ="https://commitizen-tools.github.io/commitizen/commands/bump/ "> bump command documentation</ a > .</ p >
1733
1737
< h3 id ="advanced-usage "> Advanced Usage< a class ="headerlink " href ="#advanced-usage " title ="Permanent link "> ¶</ a > </ h3 >
1734
1738
< h4 id ="get-project-version "> Get Project Version< a class ="headerlink " href ="#get-project-version " title ="Permanent link "> ¶</ a > </ h4 >
@@ -1737,8 +1741,8 @@ <h4 id="get-project-version">Get Project Version<a class="headerlink" href="#get
1737
1741
< span class ="c1 "> # Preview changelog changes</ span >
1738
1742
cz< span class ="w "> </ span > changelog< span class ="w "> </ span > --dry-run< span class ="w "> </ span > < span class ="s2 "> "</ span > < span class ="k "> $(</ span > cz< span class ="w "> </ span > version< span class ="w "> </ span > -p< span class ="k "> )</ span > < span class ="s2 "> "</ span >
1739
1743
</ code > </ pre > </ div >
1740
- < p > This command is particularly useful for automation scripts and CI/CD pipelines.
1741
- For example, you can use the output of the command < code > cz changelog --dry-run "$(cz version -p)"</ code > to notify your team about a new release in Slack.</ p >
1744
+ < p > This command is particularly useful for automation scripts and CI/CD pipelines.</ p >
1745
+ < p > For example, you can use the output of the command < code > cz changelog --dry-run "$(cz version -p)"</ code > to notify your team about a new release in Slack.</ p >
1742
1746
< h4 id ="pre-commit-integration "> Pre-commit Integration< a class ="headerlink " href ="#pre-commit-integration " title ="Permanent link "> ¶</ a > </ h4 >
1743
1747
< p > Commitizen can automatically validate your commit messages using pre-commit hooks.</ p >
1744
1748
< ol >
0 commit comments