commitizen 4.11.5__tar.gz → 4.12.0__tar.gz

{commitizen-4.11.5 → commitizen-4.12.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.3
 Name: commitizen
-Version: 4.11.5
+Version: 4.12.0
 Summary: Python commitizen client tool
 Keywords: commitizen,conventional,commits,git
 Author: Santiago Fraire
@@ -57,11 +57,11 @@ Requires-Dist: importlib-metadata>=8.0.0,<8.7.0 ; python_full_version < '3.10'
 Maintainer: Wei Lee, Axel H., Tim Hsiung
 Maintainer-email: Wei Lee <weilee.rx@gmail.com>, Axel H. <noirbizarre@gmail.com>, Tim Hsiung <bear890707@gmail.com>
 Requires-Python: >=3.10, <4.0
-Project-URL: Changelog, https://github.com/commitizen-tools/commitizen/blob/master/CHANGELOG.md
-Project-URL: Documentation, https://commitizen-tools.github.io/commitizen/
 Project-URL: Homepage, https://github.com/commitizen-tools/commitizen
-Project-URL: Issues, https://github.com/commitizen-tools/commitizen/issues
+Project-URL: Documentation, https://commitizen-tools.github.io/commitizen/
 Project-URL: Repository, https://github.com/commitizen-tools/commitizen
+Project-URL: Issues, https://github.com/commitizen-tools/commitizen/issues
+Project-URL: Changelog, https://github.com/commitizen-tools/commitizen/blob/master/CHANGELOG.md
 Description-Content-Type: text/markdown
 
 [![GitHub Workflow Status](https://img.shields.io/github/actions/workflow/status/commitizen-tools/commitizen/pythonpackage.yml?label=python%20package&logo=github&logoColor=white&style=flat-square)](https://github.com/commitizen-tools/commitizen/actions)
@@ -73,7 +73,7 @@ Description-Content-Type: text/markdown
 [![Conda Version](https://img.shields.io/conda/vn/conda-forge/commitizen?style=flat-square)](https://anaconda.org/conda-forge/commitizen)
 [![homebrew](https://img.shields.io/homebrew/v/commitizen?color=teal&style=flat-square)](https://formulae.brew.sh/formula/commitizen)
 [![Codecov](https://img.shields.io/codecov/c/github/commitizen-tools/commitizen.svg?style=flat-square)](https://codecov.io/gh/commitizen-tools/commitizen)
-[![pre-commit](https://img.shields.io/badge/pre--commit-enabled-brightgreen?style=flat-square&logo=pre-commit&logoColor=white)](https://github.com/pre-commit/pre-commit)
+[![prek](https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/j178/prek/master/docs/assets/badge-v0.json&style=flat-square&color=brightgreen)](https://github.com/j178/prek)
 
 ![Using Commitizen cli](images/demo.gif)
 
@@ -248,7 +248,7 @@ This command is particularly useful for automation scripts and CI/CD pipelines.
 
 For example, you can use the output of the command `cz changelog --dry-run "$(cz version -p)"` to notify your team about a new release in Slack.
 
-#### Pre-commit Integration
+#### Prek and Pre-commit Integration
 
 Commitizen can automatically validate your commit messages using pre-commit hooks.
 
@@ -266,7 +266,7 @@ repos:
 
 2. Install the hooks:
 ```sh
-pre-commit install --hook-type commit-msg --hook-type pre-push
+prek install --hook-type commit-msg --hook-type pre-push
 ```
 
 | Hook              | Recommended Stage |
@@ -276,7 +276,7 @@ pre-commit install --hook-type commit-msg --hook-type pre-push
 
 > **Note**: Replace `master` with the [latest tag](https://github.com/commitizen-tools/commitizen/tags) to avoid warnings. You can automatically update this with:
 > ```sh
-> pre-commit autoupdate
+> prek autoupdate
 > ```
 
 For more details about commit validation, see the [check command documentation](https://commitizen-tools.github.io/commitizen/commands/check/).

commitizen-4.12.0/commitizen/__version__.py

@@ -0,0 +1 @@
+__version__ = "4.12.0"

{commitizen-4.11.5 → commitizen-4.12.0}/commitizen/git.py

@@ -118,8 +118,8 @@ class GitCommit(GitObject):
             >>> commit.parents
             ['def456', 'ghi789']
         """
-        rev, parents, title, author, author_email, *body_list = rev_and_commit.split(
-            "\n"
+        rev, parents, title, author, author_email, *body_list = (
+            rev_and_commit.splitlines()
         )
         return cls(
             rev=rev.strip(),

{commitizen-4.11.5 → commitizen-4.12.0}/commitizen/project_info.py

@@ -6,7 +6,7 @@ from typing import Literal
 
 
 def is_pre_commit_installed() -> bool:
-    return bool(shutil.which("pre-commit"))
+    return any(shutil.which(tool) for tool in ("pre-commit", "prek"))
 
 
 def get_default_version_provider() -> Literal[

{commitizen-4.11.5 → commitizen-4.12.0}/docs/README.md

@@ -7,7 +7,7 @@
 [![Conda Version](https://img.shields.io/conda/vn/conda-forge/commitizen?style=flat-square)](https://anaconda.org/conda-forge/commitizen)
 [![homebrew](https://img.shields.io/homebrew/v/commitizen?color=teal&style=flat-square)](https://formulae.brew.sh/formula/commitizen)
 [![Codecov](https://img.shields.io/codecov/c/github/commitizen-tools/commitizen.svg?style=flat-square)](https://codecov.io/gh/commitizen-tools/commitizen)
-[![pre-commit](https://img.shields.io/badge/pre--commit-enabled-brightgreen?style=flat-square&logo=pre-commit&logoColor=white)](https://github.com/pre-commit/pre-commit)
+[![prek](https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/j178/prek/master/docs/assets/badge-v0.json&style=flat-square&color=brightgreen)](https://github.com/j178/prek)
 
 ![Using Commitizen cli](images/demo.gif)
 
@@ -182,7 +182,7 @@ This command is particularly useful for automation scripts and CI/CD pipelines.
 
 For example, you can use the output of the command `cz changelog --dry-run "$(cz version -p)"` to notify your team about a new release in Slack.
 
-#### Pre-commit Integration
+#### Prek and Pre-commit Integration
 
 Commitizen can automatically validate your commit messages using pre-commit hooks.
 
@@ -200,7 +200,7 @@ repos:
 
 2. Install the hooks:
 ```sh
-pre-commit install --hook-type commit-msg --hook-type pre-push
+prek install --hook-type commit-msg --hook-type pre-push
 ```
 
 | Hook              | Recommended Stage |
@@ -210,7 +210,7 @@ pre-commit install --hook-type commit-msg --hook-type pre-push
 
 > **Note**: Replace `master` with the [latest tag](https://github.com/commitizen-tools/commitizen/tags) to avoid warnings. You can automatically update this with:
 > ```sh
-> pre-commit autoupdate
+> prek autoupdate
 > ```
 
 For more details about commit validation, see the [check command documentation](https://commitizen-tools.github.io/commitizen/commands/check/).

{commitizen-4.11.5 → commitizen-4.12.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "commitizen"
-version = "4.11.5"
+version = "4.12.0"
 description = "Python commitizen client tool"
 authors = [{ name = "Santiago Fraire", email = "santiwilly@gmail.com" }]
 maintainers = [
@@ -107,17 +107,18 @@ test = [
     "pytest-freezer>=0.4.6",
     "pytest-xdist>=3.1.0",
     "pytest-gitconfig>=0.9.0",
+    "pre-commit>=4.5.1",
 ]
 
 linters = [
     "ruff>=0.11.5",
-    "pre-commit>=3.2.0",
     "mypy>=1.16.0",
     "types-deprecated>=1.2.9.2",
     "types-python-dateutil>=2.8.19.13",
     "types-PyYAML>=5.4.3",
     "types-termcolor>=0.1.1",
     "types-colorama>=0.4.15.20240311",
+    "prek>=0.2.28",
 ]
 
 documentation = ["mkdocs>=1.4.2", "mkdocs-material>=9.1.6"]
@@ -303,8 +304,8 @@ doc.help = "Live documentation server"
 doc.cmd = "mkdocs serve --livereload"  # mkdocs hot reload failure workaround. Ref: https://github.com/mkdocs/mkdocs/issues/4032#issuecomment-3591002290
 
 ci.help = "Run all tasks in CI"
-ci.sequence = ["check-commit", { cmd = "pre-commit run --all-files" }, "cover"]
+ci.sequence = ["check-commit", { cmd = "prek run --all-files" }, "cover"]
 ci.env = { SKIP = "no-commit-to-branch" }
 
 setup-pre-commit.help = "Install pre-commit hooks"
-setup-pre-commit.cmd = "pre-commit install"
+setup-pre-commit.cmd = "prek install"

commitizen-4.11.5/commitizen/__version__.py

@@ -1 +0,0 @@
-__version__ = "4.11.5"