`better-commits` cli utility integration

[Rnbsov]

Is your feature request related to a problem? Please describe.
Currently when creating commits with lazygit I can't create conventional commits automatically

https://github.com/Everduin94/better-commits
https://github.com/Everduin94/better-commits
https://github.com/Everduin94/better-commits

Describe the solution you'd like
A opening modal with options similiar to those that appear when using better-commits

Describe alternatives you've considered
There is also other such cli utilities similiar to better-commits, but I this one works best for me
or screenshots about the feature request here.

[stefanhaller]

This should be easy to do using a custom command, have you tried that?

[jessefarinacci]

This should be easy to do using a custom command, have you tried that?

I did, and it worked! THX @stefanhaller

diff --git a/.config/lazygit/config.yml b/.config/lazygit/config.yml
index 4b3f6d3..6d214c9 100644
--- a/.config/lazygit/config.yml
+++ b/.config/lazygit/config.yml
@@ -130,7 +130,13 @@ refresher:
 confirmOnQuit: false
 quitOnTopLevelReturn: false
 disableStartupPopups: true
-customCommands: []
+customCommands:
+    - key: 'c'
+      context: 'files'
+      command: 'better-commits'
+      subprocess: true
+      after:
+          checkForConflicts: true
 services: {}
 notARepository: quit
 promptToReturnFromSubprocess: false
@@ -215,7 +221,7 @@ keybinding:
         recentRepos: <enter>
         allBranchesLogGraph: a
     files:
-        commitChanges: c
+        commitChanges: ''
         commitChangesWithoutHook: w
         amendLastCommit: A
         commitChangesWithEditor: C

DISCLAIMER: My config file was customized from a default base of lazygit --config from a few versions ago, the diff below may not apply clean. (It'd be neat if lazygit kept all options sorted or somesuch to minimize diff artifacts between versions and overrides.)

[stefanhaller]

DISCLAIMER: My config file was customized from a default base of lazygit --config from a few versions ago, the diff below may not apply clean. (It'd be neat if lazygit kept all options sorted or somesuch to minimize diff artifacts between versions and overrides.)

Actually we don't recommend to do that. It is recommended that you keep your config file small, and add only those options that you want to change from the default.

There are two reasons for this:

1. Sometimes we have bugs where we output incorrect defaults. It's hopefully rare, but this happened with the commitPrefixes setting, for example, where copying from the defaults would result in a different behavior than omitting the key. Now of course those are bugs that we should just fix, but if you copied the broken version to your config file, then it's baked in for you and you don't benefit from the bug fix.
2. Sometimes we are being conservative with enabling options by default, trying them with a default of off for a while until we are sure that the feature is good and should be enabled for everybody. Again, if you bake the off value into your config file, then you don't benefit from what we think is an improvement for most users when we change the default to true.

[jessefarinacci]

Thanks for your explanation, I can appreciate that perspective. As a user that cares about my stuff working at all times, and the buck stopping with myself, I must reject that idea though. I don't trust upstream of any project, and I believe you to be sincere that you go above and beyond, to not change my defaults out from under me.. even if only by mistake.

Just for clarification, I did a bootstrap lazygit --config one time only, and then placed it under dotfile version control. When new versions of lazygit are released, I re-run the command on a clean tree, see what changes I want to bring in, test it out, and commit it if I like it. This mode has been working for me quite a long time across lots of tools, I find it convenient and stable.

Thank you for a great tool! :)