[Feature Request] Syntax highlighting for Conventional Commits

[ravindUwU]

Support for Conventional Commits would be a nice to have.

IMO this could provide,

• An option to opt-in for conventional commits features per repository, and during cloning.

• Detection & highlighting of conventional commit scopes at the beginning of the subject of a commit message.

[Otiel]

As much as I support conventional commits, we need to be careful not turning the UI into a Christmas tree. Some thoughts:

• A different color for each <type> (fix:, feat:, build:, chore:, ci:, docs...) may be too much.
• Should we use a different color each structural element (<type>, [optional scope], <description>...)?
• Should the list of commits be colored? Or only the commit message on the "Commit", "Changes" and "File Tree" tab?

[eng1n88r]

It's been a while. Any updates on conventional commits support?

[DanPristupov]

After 4 years conventional commits didn't become widely used.

[bdovaz]

It is a good practice in the industry to be able to generate changelogs automatically and follow a convention and that the git history is not a chaos.

It will depend on the team / project but I tell you that if it is a serious product (enterprise level) it will follow this kind of good practices.

[eng1n88r]

After 4 years conventional commits didn't become widely used. It will depend on the team / project but I tell you that if it is a serious product (enterprise level) it will follow this kind of good practices.

I think that's true to some extent. CC is a good practice, but like any methodology, it has its own set of challenges and may not be a one-size-fits-all solution.

I believe major enterprise players have their own established practices, development workflows, and release management systems (using in-house developed tooling, etc.), and this doesn't necessarily reflect a judgment on CC's usefulness or effectiveness.

@DanPristupov, I see that as a 'nice to have' feature, but I believe from your point of view, if there isn't a huge demand, it may not be reasonable to implement it. If there are no plans of adding it I guess we could conclude and close the discussion on that matter.

PS: I really appreciate Fork and use it extensively, both personally and professionally (I've purchased two licenses for these purposes). It's been a fantastic tool in my workflow. I'm quite interested in the future development of Fork, and it would be incredibly helpful to see a more 'digestible' roadmap of planned features and fixes. This would make it easier to follow along than sorting through the over 980 issues on GitHub. I'm looking forward to what's coming next!

[DanPristupov]

We are uncertain about CC. I'm afraid to add something that will bring an additional level of complexity to the source code and make maintenance more difficult while only a very few people will use it. Adding features is relatively easy, but we can't make a mistake, otherwise it will be impossible to remove it without upsetting some users.

Anyway... What do you think about the following concept? It's a screenshot of the Angular repo.

Light theme:

Dark theme:

[eng1n88r]

This looks awesome!

[DanPristupov]

Detection & highlighting of conventional commit scopes at the beginning of the subject of a commit message.

We just released Fork 1.99 which highlights commit prefixes. Only with bold.

[ravindUwU]

This looks really good Dan! 😍

Thoughts on a repository setting to colour specific prefixes or prefix patterns (globs?) a certain way? e.g., just the docs: prefix coloured idk... yellow instead of black, in the screenshot above, which would make it easier to skip past just those commits 💁.