Skip to content

Commit aba71b2

Browse files
committed
chore: trim down .cz.toml
1 parent 2ddaab9 commit aba71b2

File tree

1 file changed

+3
-32
lines changed

1 file changed

+3
-32
lines changed
Lines changed: 3 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -1,48 +1,19 @@
1-
# .cz.toml
2-
# See https://commitizen-tools.github.io/commitizen/config/
3-
4-
# Commitizen configuration for project release management (using Conventional Commits).
5-
61
[tool.commitizen]
7-
# Format for Git tags created by cz bump. '$version' is replaced by the new version.
82
tag_format = "v$version"
9-
10-
# Versioning scheme to use for deciding the next version based on commit types.
11-
# See https://commitizen-tools.github.io/commitizen/versioning/ for options.
12-
# 'pep440' (default) is common for Python (e.g., 0.1.0, 1.2.3)
13-
# 'semver' is another popular standard (major.minor.patch)
143
version_scheme = "pep440"
154

165
# Set to true to allow bumping to 0.y.z from 0.(y-1).z when commit types normally trigger major bump.
176
# Recommended for initial development phases before 1.0.0.
187
major_version_zero = true
198

20-
# Files where the version string should be updated when 'cz bump' is run.
21-
# Ensure these paths and variable names match your project.
229
write_version_files = [
23-
# Updates the [project].version in pyproject.toml (PEP 621)
2410
"pyproject.toml:version",
25-
# Example: Update __version__ in your package's __init__.py
2611
"src/{{ cookiecutter.package_name }}/__init__.py:__version__",
27-
# Add other files if needed (e.g., YOUR_APP/__init__.py for complex structures)
2812
]
29-
30-
# File where Commitizen reads/writes the commit message for manual commits (standard).
3113
commit_msg_file = ".git/COMMIT_EDITMSG"
3214

33-
# Optional: Define specific commit types and their impact on version bumping/changelog sections.
34-
# See https://commitizen-tools.github.io/commitizen/getting_started/#setting-the-cz-config
35-
# The default types are usually sufficient (feat, fix, breaking changes, etc.) but can be customized.
36-
# [tool.commitizen.commit_types]
37-
# feat = { description = "A new feature", section = "Features" }
38-
# fix = { description = "A bug fix", section = "Bug Fixes" }
39-
# chore = { description = "Build process or auxiliary tool changes", hidden = true }
40-
41-
42-
# Optional: Configuration for Git host integrations (e.g., creating GitHub releases).
43-
# See https://commitizen-tools.github.io/commitizen/changelog/#git-host-configuration
4415
[tool.commitizen.github]
45-
release = true # Enable GitHub release creation
46-
release_asset_path = "dist/*" # Attach build artifacts from the 'dist' directory
16+
release = true
17+
release_asset_path = "dist/*"
4718
release_asset_descriptions = { "*.tar.gz": "Source distribution", "*.whl": "Python Wheel" }
48-
base_url = "https://github.com/{{ cookiecutter.github_username | lower | replace(' ', '-') }}/{{ cookiecutter.project_slug.replace('_', '-') }}" # Your repo URL
19+
base_url = "https://github.com/{{ cookiecutter.github_username | lower | replace(' ', '-') }}/{{ cookiecutter.project_slug.replace('_', '-') }}"

0 commit comments

Comments
 (0)