chore: update cliff.toml #58

Merged

abart27 merged 1 commit from update-cliff-config into main

2026-03-09 21:41:33 +00:00

abart27 commented

2026-03-09 21:41:28 +00:00

(Migrated from github.com)

No description provided.

copilot-pull-request-reviewer[bot] (Migrated from github.com) reviewed

2026-03-09 21:44:58 +00:00

copilot-pull-request-reviewer[bot] (Migrated from github.com) left a comment

Pull request overview

Updates the repository’s git-cliff configuration, affecting how changelogs are rendered and how commits are filtered/grouped for release notes generation.

Changes:

Simplifies the changelog header/body templates and removes the version/unreleased heading block from the body template.
Adds a commit-skip rule for changelog: skip (including a raw_message-based rule) and sets preprocessors/postprocessors to empty arrays.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

## Pull request overview Updates the repository’s `git-cliff` configuration, affecting how changelogs are rendered and how commits are filtered/grouped for release notes generation. **Changes:** - Simplifies the changelog header/body templates and removes the version/unreleased heading block from the body template. - Adds a commit-skip rule for `changelog: skip` (including a `raw_message`-based rule) and sets preprocessors/postprocessors to empty arrays. --- 💡 <a href="/mupen64/ugui/new/main?filename=.github/instructions/*.instructions.md" class="Link--inTextBlock" target="_blank" rel="noopener noreferrer">Add Copilot custom instructions</a> for smarter, more guided reviews. <a href="https://docs.github.com/en/copilot/customizing-copilot/adding-repository-custom-instructions-for-github-copilot" class="Link--inTextBlock" target="_blank" rel="noopener noreferrer">Learn how to get started</a>.

cliff.toml

The body template no longer renders a per-release heading (version/timestamp or an unreleased section). This makes the generated changelog ambiguous because groups will be listed without any release boundary. If this wasn’t intentional, reintroduce a release header block (e.g., version/unreleased) before iterating groups, or add an explicit heading so consumers can tell which release the entries belong to.

The `body` template no longer renders a per-release heading (version/timestamp or an `unreleased` section). This makes the generated changelog ambiguous because groups will be listed without any release boundary. If this wasn’t intentional, reintroduce a release header block (e.g., version/unreleased) before iterating groups, or add an explicit heading so consumers can tell which release the entries belong to.

cliff.toml

The comment says the footer field is currently broken, but this config still includes a footer-based skip rule. This is contradictory and makes it unclear which rule is expected to work. Either remove the footer-based parser (and rely on the raw_message rule), or update the comment to explain why both are needed and when the footer rule will become effective.

  { message = "^doc", group = "📚 Documentation" }

The comment says the `footer` field is currently broken, but this config still includes a footer-based skip rule. This is contradictory and makes it unclear which rule is expected to work. Either remove the footer-based parser (and rely on the `raw_message` rule), or update the comment to explain why both are needed and when the footer rule will become effective. ```suggestion { message = "^doc", group = "📚 Documentation" } ```