I'm still not very good at making my Git commit messages (for my blog repo) look good; I'm often just trying to dump all the self-reminders/notes in there kind of messily.
I now know (a bit late):
1. The first line is the most important and should be <50 characters with no period
2. There should be a blank line after the first
3. The rest can be up to 72 char.
I hope one day my commit messages can be clean and consistent!
Good guide here: https://wiki.openstack.org/wiki/GitCommitMessages
🚀 Wow, now you can relive your Git commits as a ✨fascinating✨ animated movie. Because we all know that turning your code history into a cinematic experience is exactly what the terminal was missing. 🎥🎉
https://github.com/unhappychoice/gitlogue #GitCommits #MovieMagic #AnimatedCoding #TerminalExperience #HackerNews #ngated
🚀 Ah yes, the groundbreaking #innovation of #government #meetings via Git commits. 🤓 When you thought #bureaucracy couldn't get any slower, they found a new way to fork it up! 💾 #EfficiencyRedefined
https://codeberg.org/forgejo/sustainability/pulls/137/files #GitCommits #EfficiencyRedefined #HackerNews #ngated
Meeting notes between Forgejo and the Dutch government via Git commits
https://codeberg.org/forgejo/sustainability/pulls/137/files
#HackerNews #MeetingNotes #Forgejo #DutchGovernment #GitCommits #Collaboration
In the context of #gitcommits or #githistory what story would you find more useful?
1. I developed A and B simultaneously B solves a problem for A which depends on B.
2. I developed A in its entirety, and then made this abstraction into B from A
