Hacker News Reader

If you find that using git is taking up a lot of your time, the first thing you should do is switch to a good GUI, which saves 90% of your time anyway. Automating the fastest and easiest part of using git is penny-wise and pounds-foolish.

View on HN

git commands are generally faster than a GUI once you learn them but some engineers still struggle with wording the commit message regardless of what tool they use.

If the wording of the commit message is the issue, there are ways to reduce the toil without having AI confabulate a message. Conventional Commits <https://www.conventionalcommits.org/en/v1.0.0/> has been discussed on HN many times. The 50/72 practice (some tools will help with this) <https://tbaggery.com/2008/04/19/a-note-about-git-commit-mess...> and many many words out there suggesting some best practices.

A team can and should work out their own best practices. A git prepare-commit-msg hook can provide a template for message conventions. Perhaps there's room for a tool or UI enhancement to provide additional guidance.

There is no universe in which remembering and typing git commands is more efficient than clicking a single button. Just the mistakes from git CLI use are a major time waster.

Good GUIs roll up multiple commands into easy actions and can even automate your team's workflow.

Reply on news.ycombinator.com