4 ms·
I stated using gofakeit's "hackerphrase" for all commit messages. https://github.com/andrewarrow/feedback/commits/main/ https://github.com/andrewarrow/feedback
by andrewfromx 3y ago
I stated using gofakeit's "hackerphrase" for all commit messages.
https://github.com/andrewarrow/feedback/commits/main/ https://github.com/andrewarrow/feedback/commits/main/
hp | git commit -a -F -
hp is a golang binary that just spits out a hacker phrase. I have this aliased with the letter q for "quick" so I'm always checking in stuff with q return push done.
- karmajunkie 3y agoI've been using opencommit[1] and have been pretty happy with the summaries its generating. I usually add a one liner at the top to summarize the reason for the PR but it saves me a lot of typing documenting what was actually done at a high level. [1] https://github.com/di-sukharev/opencommit https://github.com/di-sukharev/opencommit
- lexicality 3y agothat's a great idea but you can make it even more efficient head -c50 </dev/urandom | xxd -p -u | git commit -a -F - That way you'll never accidentally overflow the commit message first line length and no one will even begin to think that the messages might mean something!
- andrewfromx 3y agothis is great. If I do a mix of these + hacker phrase I'll be able to find a commit like, "oh yeah, it's the one right after the urandom bytes.