Git push origin master

>git push origin master

Attached: 516515154.jpg (1068x601, 65K)

>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

Attached: longchad.jpg (680x1253, 50K)

>git branch master-2
>git checkout master-2

Attached: 1510088355781.png (550x511, 534K)

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!!!

Attached: 1544729016111.png (1098x1126, 492K)

>git checkout --orphan new_root_branch && git commit && git push --force

Attached: tret.png (621x1103, 146K)

>gets fired

Attached: 831-8318812_view-samegoogleiqdbsaucenao-based-pepe-in-a-tuxedo.jpg (820x836, 154K)

>unique commit messages

Attached: 1509754617976.jpg (960x960, 84K)

>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

Attached: maxresdefault.jpg (1280x720, 47K)

>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

Attached: 1555889254008.jpg (958x900, 70K)

>working only with stashes

Now thats based.

what does that even mean

Kek

>git checkout origin master
>git reset --hard

Attached: 1555468524993.jpg (1080x1207, 98K)

>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

Attached: 32f.jpg (822x960, 50K)

reset defaults to soft you retard

based smoothbrain likes implicitness

>I only publish code when it's in a working state.

Attached: 1563377100139.jpg (474x588, 33K)

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

Attached: Install_gentoo.jpg (640x360, 54K)

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 ?