3 ms·
Really depends on the project. For spinning up an MVP in ~1 week, there's very little benefit wasting time on thoughtful commit messages, because i) you're high
by nomilk 3y ago
Really depends on the project. For spinning up an MVP in ~1 week, there's very little benefit wasting time on thoughtful commit messages, because i) you're highly unlikely to use them for anything, ii) in an absolute disaster scenario, just rebuild the whole app - at most you lose a few days.
For a recent project, I didn't push to GitHub for about 8 weeks. No point. Just one extra step. Only benefit is if I lose my laptop I've got a backup. But there's a backup on heroku. So the only time I'd need the GitHub version is if both my laptop went missing (hasn't ever happened, but I cede it could happen), and heroku somehow loses it (again, has never happened, but I guess it could).
- maccard 3y agoMy method is slightly different. For pet projects, I work on main until I deploy something, and I push to GH when it's building/running at the end of a session. I do git commit initially, and then "amend" as I go with intellij/goland's one click UI. I try to write one line commit messages, mostly for posterity. Ive had some nice moments looking back on the "OMG it works" projects