>git push origin master
Git push origin master
>he doesn’t use —force
Based, only faggots use branches other than master
What's so Chad about that? I only publish code when it's in a working state.
>git checkout master
>git commit
>git branch master-2
>git checkout master-2
You're image isn't fooling anyone. Try this.
>git add . && git commit -m "benis" && git push origin master
so that means your code isn't in 100% working state 100% of the time?
what a fucking cuck
It's like sliding your penis into a vaginal receptacle.
>does nothing
nothin personnel, cs grad
>git add node_modules
>NOOO Stop him officer!!!
>git checkout --orphan new_root_branch && git commit && git push --force
>gets fired
>unique commit messages
>no one but you takes the time to write coherent commit messages
why do people do this
>WIP
>WIP
>WIP
>WIP
>Refactor
>git push origin master --force
>not being scared of the --force command thingy
Youre too reckless :(
I used to only do this, but recently I got told to make a branch so there would be better track of what I'm doing
>chad masterpusher:
>code works perfect, no need for other branches
>push triggers CI, so clients can see his work immediately on prod
>erases all virgin topicbrancher commits, no rebase
while true; do git push -f master; done
>working only with stashes
Now thats based.
what does that even mean
Kek
>git checkout origin master
>git reset --hard
>why yes, i did get a degree in computer science, how do you know?
rm -rf * && git add . && git commit -m "nothing personell" && git push origin master --force
might as well make the message: "nothing"
xDDDDDDDDDDDDDDDDDD
:)
>git reset --soft HEAD~10
>git commit -m "committed by Chad"
>git push -f
reset defaults to soft you retard
based smoothbrain likes implicitness
>I only publish code when it's in a working state.
Im wondering if you could setup a script that would roll back one commit a week that way, how much time would it take for them to figure that out.
>git commit -m "link fix"
>git stash is the chaddest way to version control
If you were on a different branch you did literally fucking nothing though.
Virgin no stasher over here. Everyone laff at this loser.
> git commit -m "typo fix"
git commit -m "PM\'d you the fix"
is it bad to do that?
kek
Yes you shouldnt bother making a commit for a singular change.
Instead try to always mush as many changes as you can into a single commit.
Preferably changes from many files that are not related together.
You guys aren't even deleting the history and rebasing I just undid all this shit
>Not having master branch push protected.
>Not enforcing reviews and unit test jobs on code reviews.
What the fuck did you learn in your drugasoft class ?