>check commit history
>see this
why's this allowed
Check commit history
Cameron Ward
Other urls found in this thread:
docs.gitlab.com
twitter.com
Nicholas Barnes
ban him.
Sebastian White
I can't ban my coworkers from my company's project
David King
>100s of commits
>squashes them into one
here's your commit bro
Connor Baker
I do that sometimes when a test is passing locally but failing on CI
Hunter Hall
literally standard practice at my work
end me pls
Jace Phillips
In my work usually there are no messages, or the messages are so vague there is no way of looking for exact changes but the project and date.
Ayden Howard
tell your manager to ban him.
Parker Martin
oh don't worry, we got some of that too
Carter Lee
Just filter them like I filtered you few secs ago
Alexander Ortiz
people who leave no commit messages deserve the utmost painful of deaths
Bentley Thomas
How detailed should my commitessages be? I always feel like Im never saying enough, but i dont want to write paragraphs either.
Levi Howard
Detailed enough that I understand what you did in your commit from the first read through, but don't go into specifics, that's what the code is for. General rule of thumb is, Keep each change detail to a single sentence. If you absolutely must go into further detail, put a little addendum/asterisk/notes section at the BOTTOM of the commit.
Aiden Jackson
"Fixed stuff."
Noah White
Use githooks where you can. Helps standardize commit messages nicely.
Jason Price
This is far too fucking detailed. Just put a one sentence summary of the changes. If you want details compare it nigger.
Sebastian Brooks
>why's this allowed
It isn't.
docs.gitlab.com
Liam White
>check out a project my coworker is doing
>__pycache__ committed
>input.csv committed
>output.csv committed
>miscellaneous thing.xlsx committed
>error.log committed
>commit messages have nothing to do with these files
>.gitignore ignores the .csv files, but it doesn't matter since they were already added and he didn't remove them
He only knows 3 git commands and is satisfied with it.
git add .
git commit -m "changed x and now it does y"
git push
Hunter Richardson
my issue is too long commit messages. it is still one sentence but overly verbose
William Howard
Explain why you made changes, not what you actually did. Also link an identifier to the task that is created for the changes from JIRA or whatever software you use.
Joseph Hughes
Now the "TeSt" ones don't look so bad, do they?