Why you should use a terminal editor to write a commit message
joaomagfreitas.link
Why you should use a terminal editor to write a commit message
1–10 of 32 posts
Re: Why you should use a terminal editor to write a commit message
#2Re: Why you should use a terminal editor to write a commit message
#3I do find value in your approach, but I'm just so used to the -m approach that I would hesitate to use another one. It helps me make sure to be brief and get to the point with the commit. The editor would give me too much freedom and I am likely to ramble!
Re: Why you should use a terminal editor to write a commit message
#4I just use VS Code's commit message box, easier than CLI in my opinion (I also like VS Code's git commit flow)
Re: Why you should use a terminal editor to write a commit message
#5I do find value in your approach, but I'm just so used to the -m approach that I would hesitate to use another one. It helps me make sure to be brief and get to the point with the commit. The editor would give me too much freedom and I am likely to ramble!
> The editor would give me too much freedom and I am likely to ramble!
Please do! Context not included in the commit message or the code is lost forever.
How to Write a Git Commit Message: https://cbea.ms/git-commit/
Re: Why you should use a terminal editor to write a commit message
#61, 2.: This expense of time is about as much as it takes for the editor to open, and then to close it again.
4. Pre-commit hooks are an anti-pattern. The repo creator has no business messing with my local, half-broken experiment/exploration commits. Do that on push if you must.
5. The dual: oh, you passed the wrong flags to commit and you remembered this after you started to write the commit message? Too bad, the mess is yours to fix now.
The one reason that completely convinces me is 3. It's not worth the pain to enter a multi-line commit on the command-line. -m is for one-liners.
Re: Why you should use a terminal editor to write a commit message
#7I just use VS Code's commit message box, easier than CLI in my opinion (I also like VS Code's git commit flow)
> All of these issues can be avoided
... if you use a gui in front of git :)
Re: Why you should use a terminal editor to write a commit message
#8I mostly just use whatever my IDE provides to do commit messages ¯\_(ツ)_/¯
Other than that, this feels over the top, to the point of satire on opinions in tech?
If typing two extra characters actually does cost you valuable time then you possibly need to reevaluate your work pressure or possibly amount of commits.
If you have trouble finding quotes on your keyboard, your blind typing skills just suck. Also, what language are you even coding in?
Remembering to not press enter is on the same level as learning to use nano (use vi you peasant!).
I guess some of the arguments are valid... in some environments.
Re: Why you should use a terminal editor to write a commit message
#9I use an alias for `git commit -m`
Re: Why you should use a terminal editor to write a commit message
#10[deleted]