they made me do this for some time. the funniest part was that the "code reviewer" would usually push +1kloc commits with no message or description whatsoever. they are going to have to pay me more if they don't want me to just >git commit -m "fix some stuff"
5 minutes before clocking out
>No, the code reviewer will tell you to write a summary in the commit message or it wont get accepted. You also need to reference the jira task number
Just work at a shit java shop and you won't have to do any of this.
t. works at a shit java shop.
Nah, not going to add unnecessary steps into my workflow bud. Sticking with the -m flag. KISS
2 years ago
Anonymous
I don't use "-m" because >so I don't commit a half written message by accident >to use the comments under the commit as a limit to the length of the commit >makes it easier to use the command from the history
It's KISS-kino
i wish my sister was like her
she did not act like this in the anime
The anime is shit and you should know it if you watched it to the end
git push -f origin master
We use main now instead of master. Thanks.
git push -f origin :main master
>echo Black person >LICENSE.md
>git add LICENSE.md
>git commit -m "Add license"
>git push
command not found: LICENSE.md
Wingay detected. When will you switch to an actual operating system
>Does not begin with present tense verb
ngmi
git commit master
git commit sepuku
...is this wrong???
will i get fired if I do this as a jr?
No, the code reviewer will tell you to write a summary in the commit message or it wont get accepted. You also need to reference the jira task number
>You also need to reference the jira task number
glad I don't have to put ticket numbers in my commits anymore, it's the most moronic fricking shit
why? works fine
i'd rather use https://www.conventionalcommits.org/en/v1.0.0/ though
Just use a pre commit hook to add the jira id
It's a way to satisfy some audit requirements
they made me do this for some time. the funniest part was that the "code reviewer" would usually push +1kloc commits with no message or description whatsoever. they are going to have to pay me more if they don't want me to just
>git commit -m "fix some stuff"
5 minutes before clocking out
>No, the code reviewer will tell you to write a summary in the commit message or it wont get accepted. You also need to reference the jira task number
Just work at a shit java shop and you won't have to do any of this.
t. works at a shit java shop.
>committing using the "-m" flag
alternatives?
>git commit
>*git opens your default terminal text editor*
>type message
>save
Nah, not going to add unnecessary steps into my workflow bud. Sticking with the -m flag. KISS
I don't use "-m" because
>so I don't commit a half written message by accident
>to use the comments under the commit as a limit to the length of the commit
>makes it easier to use the command from the history
It's KISS-kino
That's hardly the problem. There literally isn't even anything wrong with it.
It's perfectly fine if you don't want to add a description
All my longest commit messages are fueled by unadulterated rage at some bullshit like this.
#ifdef _WIN32
printf("I don't want to deal with non-POSIX headers.");
return 0;
#endif
have you guys heard of subversive svn before? it's pretty old school and hip
git add .
git commit -m "the needful"
git push --force
as a nigerian, from my m1 air 2020 16gb ram 256gb ssd
git add -A
git commit -m "xxxx"
git push -f origin master
>git push origin master
git add sister sex
>git commit -m "stuff"