feat(render): dim housekeeping commits by default

[kylo252]

use LazyComment highlight group for commits with housekeeping types, i.e. chore/ci/doc

Inspired by refined-github

Log view

[kylo252]

@folke, this is just a minimal example implementation that can definitely be improved

[folke]

I like it! I just pushed some small improvements. Let me know what you think!

[kylo252]

I like it! I just pushed some small improvements. Let me know what you think!

Perfect! I've been thinking it would be great to add a new hl group for this, but wasn't sure how to handle the fallback.

[folke]

Merged. Thank you!

[kylo252]

@folke, some future improvements to consider

• make the list of dimmed words configurable
• add the ability to group such commits and fold them
• add the ability to skip showing these commits altogether (alter git log sub-command)

the last two will be tricky when the log only contains such commits

[folke]

For your first point, people can already do that by changing those values in the view config module.

I keep all ui related stuff in there that i don't think should be easily configurable, but can be if users want to. Keymaps etc are in there as well

[briandipalma]

add the ability to group such commits and fold them

I wouldn't reorder commits. It's handy to see what changes there are in different plugins by jumping onto the repo site and scrolling through the commits, starting from the first change. If you reorder you don't know for sure which is the first change.

[kylo252]

If you reorder you don't know for sure which is the first change.

you still have the timestamps.

I was mostly thinking of categorizing the commits within each block, e.g. similar to https://github.com/orhun/git-cliff

[canvanaut]

Hi, is it possible to only dim commits that aren't breaking (e.g. chore: foo is dimmed, but chore!: foo is not)

[kylo252]

Hi, is it possible to only dim commits that aren't breaking (e.g. chore: foo is dimmed, but chore!: foo is not)

@canvanaut, it should be doable, but the question is should we actually encourage this behavior in the first place? why introduce a breaking change in a "chore" commit in the first place? 🤔

[canvanaut]

Oh I just used that as an example, but I've seen plenty of refactor!: foo, which doesn't get highlighted since I've made regular refactor: foo dimmed.