Review of log level usage: promote certain trace! logs to info! to improve observability

[ognis1205]

As seen in issues like #1189 and #1181, it appears that some log messages that could aid in understanding git-cliff’s behavior or detecting misconfigurations early are currently logged at the trace! level.

This effectively hides them unless users explicitly pass -vv, which might not be intuitive for many users and may hinder:

• Early detection of configuration or tagging issues
• Understanding how git-cliff is interpreting tags, commits, or configs
• General user confidence in how git-cliff is working under the hood

💡 Proposal

Review current trace! log usage and consider promoting messages that reflect high-level behavior (e.g., tag skipping, changelog generation decisions, applied filters) to info!.

This would make git-cliff -v (or even no -v) much more informative without overwhelming the user, while still preserving trace! for deeply internal logic.

✅ Benefits

• Easier for users to understand what git-cliff is doing
• Faster troubleshooting

[orhun]

That's actually a pretty good idea! I would love to see this happen :D

Do you have time/interest to work on this after the upcoming release maybe?

[ognis1205]

Sounds good — I’m happy to take this on after the upcoming release!

Before that, I’ll put together a quick guideline on what kind of logs we want and at what level, and share it here so we’re on the same page.

[orhun]

Sounds perfect, thanks!

[ognis1205]

TODO: Reminder to initiate this task following the release.

[orhun]

Yeah, would be nice to have this for the next release!