this post was submitted on 03 Nov 2023
30 points (67.4% liked)
Programming
17366 readers
457 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Why don’t you spend time on commit messages though?
I make really small and really frequent commits. Like I'll commit all changes every 10 min regardless of if a feature is done or not, and basically use commits like an undo button.
I still use git history a lot (per file history usually) but even when browsing years and hundreds of commits into the past, I don't really need detailed/thoughtful messages to find the change I'm looking for. Binary search plus those 2 or 3 word message hints are lightning fast. And the number of times I commit vastly outweighs the number of times I browse the history.
When it comes to documentation and other people, feature-branches are my "OK I fully finished this thing; here's a summary". I'm also not afraid to squash a ton of useless commits together right before making a PR.
TDLR; spending more than 3 sec doesn't help future me or current me, so it's a waste of time