|
WHEN APPLIED THIS POST WILL EXPOSE ME AS A FIVE FIGGY FUCKTARD
|
# ? Mar 4, 2017 02:15 |
|
|
# ? May 18, 2024 09:32 |
|
commit messages should be past tense not imperative. that guide is trash
|
# ? Mar 4, 2017 07:38 |
|
past tense wastes characters. it's a p good guide
|
# ? Mar 4, 2017 08:48 |
|
Bloody posted:commit messages should be past tense not imperative. that guide is trash
|
# ? Mar 4, 2017 16:39 |
|
Bloody posted:commit messages should be past tense not imperative. that guide is trash fritz posted:when
|
# ? Mar 4, 2017 18:55 |
|
Bloody posted:commit messages should be past tense not imperative. that guide is trash imperative makes sense to me. each commit is a patch that will <do whatever>.
|
# ? Mar 4, 2017 18:56 |
|
jony neuemonic posted:imperative makes sense to me. each commit is a patch that will <do whatever>. dammit they call it history for a reason
|
# ? Mar 4, 2017 19:32 |
|
hot take: both are fine probably imperative is better tho
|
# ? Mar 4, 2017 20:00 |
|
I have a coworker who does the
thing with his commits, but 1) it's not actually code i work on 2) he smooshes @ merge time and writes really great longform comments I'm conflicted
|
# ? Mar 4, 2017 20:01 |
|
DaTroof posted:dammit they call it history for a reason i mean, it's not a religious thing. in real life i just do whatever my team does.
|
# ? Mar 4, 2017 20:07 |
|
jony neuemonic posted:imperative makes sense to me. each commit is a patch that will <do whatever>. im about to blow ur mind functional commit message
|
# ? Mar 4, 2017 22:17 |
|
The declarative simple present has been out of fashion in English since ~the 17th century but other languages still use it and its time for a comeback imo
|
# ? Mar 4, 2017 23:18 |
|
carry on then posted:im about to blow ur mind
|
# ? Mar 4, 2017 23:23 |
|
|
# ? May 18, 2024 09:32 |
|
VOTE YES ON 69 posted:I have a coworker who does the if they squash and force push the branch at merge time and write a great commit that's good and fine
|
# ? Mar 5, 2017 04:18 |