damn I fucking love writing really long context giving commits to explain a rather deceptively simple change to things that's not that large of a diff and the history of why this is the correct fix for the quick fix . My coworkers will love me. I call this move the @sgrif commit.
-
Show this thread
-
(1/10)xEngiNieR: Automata Retweeted (1/10)xEngiNieR: Automata
It's one of my real good commit messages but I can't show it here :( so here's an example of what I mean when I write them:https://twitter.com/mgattozzi/status/1204632323498618885 …
(1/10)xEngiNieR: Automata added,
2 replies 0 retweets 7 likesShow this thread -
Replying to @mgattozzi @sgrif
That's a good example. When I first started coding I'd just write the functional change. But after having that bite me in the ass, I've gotten a bit more detailed about not just what changed by why we changed it to help analysis for later. could always do better, as demonstrated
1 reply 0 retweets 1 like
Personally I tend to leave out what changed beyond the title. Folks can see the diff. If what changed isn't clear from the code than the code should be improved
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.