Configure from section in pyproject.toml

[radusuciu]

It would be great for Python projects if git-cliff could be configured from pyproject.toml as can be done for Rust projects in Cargo.toml (implemented in #46). I think the implementation would require minimal additional changes.

The docs give this as an example for Rust projects:

[package]
name = "..."
[dependencies]
# ...
[package.metadata.git-cliff.changelog]
header = "All notable changes to this project will be documented in this file."
body = "..."
footer = "<!-- generated by git-cliff -->"
# see [changelog] section for more keys
[package.metadata.git-cliff.git]
conventional_commits = true
commit_parsers = []
filter_commits = false
# see [git] section for more keys

pyproject.toml would look like:

name = "..."

[project]
dependencies = []

[tool.git-cliff.changelog]
header = "All notable changes to this project will be documented in this file."
body = "..."
footer = "<!-- generated by git-cliff -->"
# see [changelog] section for more keys
[tool.git-cliff.git]
conventional_commits = true
commit_parsers = []
filter_commits = false
# see [git] section for more keys

The format of pyproject.toml is detailed in PEP621 and the [tool] table is described in PEP518.

Looking at the implementation in f48d207 it seems that you could add a regex to support this:

/// Regex for matching the metadata in Cargo.toml
const CARGO_METADATA_REGEX: &str =
	r"^\[(?:workspace|package)\.metadata\.git\-cliff\.";

/// Regex for matching the metadata in pyproject.toml
const PYPROJECT_METADATA_REGEX: &str =
	r"^\[(?:tool)\.git\-cliff\.";

[orhun]

That's actually a great idea! Let's proceed with the implementation.

[orhun]

Implemented in #147