orhun/git-cliff

Is there an existing issue or pull request for this? I have searched the existing issues and pull requests Feature description We can match commits in commit_parsers like so: commit_parsers = [ # Rewrite history { sha = "20246539df88431c72d65d7d0d1b82fba3deec34", group = "<!-- 0 -->Added" }, # Initial commit ] However, this is a bit of a hassle since git cliff -vv dumps the short SHA e.g., TRACE git_cliff_core::process > process_commits: 2024653 - Grouping error: `Commit does not belong to any group` (Initial commit) I had quite a few and while it wasn't too hard to get the full SHAs, it would be much easier if we could just block copy the short SHAs you already printed out. Short SHAs (7+ chars) should be plenty for most repos, but people could always use more so any number of unambiguous chars should be supported, erring if there is any ambiguity just like git would. Desired solution Support any number of unambiguous short SHAs and err like git would when an

Is there an existing issue or pull request for this? I have searched the existing issues and pull requests Feature description It would be nice if commit types can be considered for the version bump but not for the changelog, and vice versa. Currently, you can only exclude commit types entirely. From #1564: I only want to include certain commit types in my CHANGELOG.md, like feat and fix, but exclude less important types like docs. So I went with the following config: commit_parsers = [ { message = "^feat", group = "<!-- 0 -->🚀 Features" }, { message = "^fix", group = "<!-- 1 -->🐛 Bug Fixes" }, ] filter_commits = true Now let's say I need to make a release which only contains one docs commit. Then git-cliff -u --bumped-version says there is nothing to bump. With filter_commits = false, it correctly calculates the next patch version, but the docs commit is included in the changelog. Is there any way to make this possible? It's basically the inverse of #1520. Not sure

Is there an existing issue for this? I have searched the existing issues Description of the bug When generating the Changelog for a repository using the GitLab integration, the commit author is used instead of the GitLab username. This behavior is unexpected and goes against the current GitLab Integration documentation. Steps To Reproduce To reproduce this bug: Setup a GitLab project to use git-cliff: [remote.gitlab] owner = "nbelste1" repo = "git-cliff-example" Example: https://gitlab.com/nbelste1/git-cliff-example/-/blob/feature/init/cliff.toml Set up a GitLab CI/CD pipeline job to run using the integration Example: https://gitlab.com/nbelste1/git-cliff-example/-/blob/feature/init/.gitlab-ci.yml Make commits authored by your GitLab account credentials (same email) Example: https://gitlab.com/nbelste1/git-cliff-example/-/commit/65cd6548a62a7d1e6c573726d6a358b0e0521061 Review the Changelog generated by git-cliff -r . ## What's Changed * initial README by @Nathan Belsterli

Is there an existing issue or pull request for this? I have searched the existing issues and pull requests Feature description The project currently uses tsup as its build tool. However, tsdown is intended to replace tsup in the future and is actively positioned as its successor. Desired solution Migrate the project from tsup to tsdown following the official migration guide: https://tsdown.dev/guide/migrate-from-tsup Alternatives considered Continuing to use tsup until it is officially deprecated Additional context #1382 (comment)