Dude! We have toilets on each floor. Why do you push shit on git?

alias wow="git status"
alias such="git"
alias very="git"

Result:

$ wow
$ such commit
$ very push

git everywhere

Just had a fire drill at school. I yelled "GIT PUSH!! GIT PUSH!!".

I've always wanted to do that... :P

I think I just broke the (only) USB C port on my MacBook so I’m racing to push about 30 git repos before the battery dies forever

When you stare into git, git stares back.

It's fucking infinite.

Me 2 years ago:
"uh was it git fetch or git pull?"

Me 1 year ago:
"Look, I printed these 5 git commands on a laptop sticker, this is all I need for my workflow! branch, pull, commit, merge, push! Git is easy!"

Me now:
"Hold my beer, I'll just do git format-patch -k --stdout HEAD..feature -- script.js | git am -3 -k to steal that file from your branch, then git rebase master && git rebase -i HEAD~$(git rev-list --count master..HEAD) to clean up the commit messages, and a git branch --merged | grep -v "\*" | xargs -n 1 git branch -d to clean up the branches, oh lets see how many words you've added with git diff --word-diff=porcelain | grep -e '^+[^+]' | wc -w, hmm maybe I should alias some of this stuff..."

Do you have any git tricks/favorites which you use so often that you've aliased them?

Git add .
Git commit -m 'stuff'
Git push
Error: merge conflict in 594 files

Git commit suicide

I know all the git commands:
- git status
- git add
- git commit
- git push

git add -A
git commit -m "fixed tupo"
git push

🤓

8am. Fire alarm. Git push!

Wife : School tooday ?
Me: Nop... Remote working ! 😎😁

Love programming

Wife : But how people know you working.

Me : git commit -a -m "im working on it" && git push

Wife : ohh never mind have a good day !

Me : you too

Wife: commit, and come to bed..
Me:
> git commit -m "wife wants me to go to bed"
> git push origin master -f

Learn git. For real. Not just git pull and git push. Setup git with a mergetool and do the gitimmersion tutorial. Be the gitmaster!

alias yolo="git push --force"

git status
git add .
git commit -m "Minor changes.."
git push
...
git status
*closes terminal*
...
"Fuck that char in that variable name isn't meant to be a capital!"
*makes change*
git status
git add .
git commit -m "Minor changes.."
git push
...
git status
*closes terminal*

In case of fire:

Git commit
Git push
Git out of building

GIT PUSH LIVE

Share your most useful terminal aliases and functions.

alias gs='git status'
alias gcm='git commit -m'
alias push='git push'
alias pull='git pull'
alias hosts='sudo nano /etc/hosts'
alias glog='git log --graph --oneline --decorate -n 10 --color'
alias mykey='cat ~/.ssh/id_rsa.pub | xclip -sel clip'

function mkcd () {
mkdir -p -- "$1" && cd -P -- "$1"
}

As well as one for each major project (lets say 1+ weeks of dev time) to immediately cd to it from anywhere. How about you guys?

Always looking to improve my terminal commands, so am curious what everyone else uses for shortcuts.

Don't forget to Git commit

Git....
alias such=git
alias very=git
alias wow=‘git status’
$wow
$ such commit
$ very push

Oh boy look at the time. It's already screw-up o' clock.

git push --force origin master

Me: git commit -a
Git: [successful]
Me: git push
Git: [unpulled commits on remote]
Me: git damnit

That moment when you sit down at your PC and realize you forgot to push your latest commit from your laptop.

$ git push --force origin master

Went into bed with peace in mind. Updated my website and everything working perfectly. Tonight I'll have a good sleep.

Jumped from bed all of a sudden :

GIT COMMIT! GIT PUSH!

With all of this Microsoft blacklist and master bullshit, I wonder when will someone protest for git push/pull to be changed due to sexism 🙄🙄🙄

Git push, Git commit, Run 😎😋

- Hey it's lunch time!
- Yeah let me push these changes...
- No! You'll do it later.
- But, it will take 2 minutes!
- NO! WE'RE HAVING LUNCH NOW.

Windows crashes ._.

* git add .
* git commit
* git push
* git the f*ck out

The only time I don't confuse push/pull is when using git.

> git commit -m 'fixing what I broke earlier'
> git pish
> git: 'pish' is not a git command. See 'git --help'.

Did you mean this?
push
> you know I meant push, why can't you leave me alone and just do it

alias such=git
alias very=git
alias wow='git status'

$ wow
$ such commit
$ very push

git pull
git push
git pull
git push
git merge XY
git release vNewBaby

Everytime I see one of my mates use git push force...

git dammit

when you push to master by mistake

So I was playing Formula 1 game and I heard “push, push, push” from the engineer while leaving pit-lane.

I immediately closed game and started “git push”

guy add proposal.txt;
git commit -m "Wish me luck";
git push

My friend and I were watching a documentary about Salmon. He suddenly starts to giggle and I ask him whats up.

Friend: Why do salmon suck at version control?

Me: why?

F: because they always git push force upstream 😂😂😂

Alright so im a highschool student and I just got sent down to the office for using putty to push to git because it's hacking. Wtf.

3 Easy step to learn and use git :
1. git commit
2. git push
3. git gud

As we may all messed up a (git) repo at the begininng, do you know the surge of adrenalin right before pushing your committed changes or merging branches?

Probably posted before, still funny!

alias yolo='git commit -am "DEAL WITH IT" && git push -f origin master'

git add *
git commit -am "stuff"
git push -f origin master

No regrets

I just saw

`git add . --all&&git commit -m update&&git push`

as a npm script hook m) I don't even care, just surprised it wasn't named yolo.

Seen another dev push changes to a production server without even committing it to git.

got commit
got add
got pull
got push
...

Typos.. every.. Damn.. time.. so I assigned an alias for got = git

Don't want to break your commit streak on Github.
So you change one line and :-
git add .
git commit -m "Minor Tweak"
git push

VOILA ! the box is green for today . *Evil Smile*

the moment when you remember you forgot to push

!rant.
Here's some useful git tricks. Use with care and remember to be careful to only rewrite history when noones looking.

- git rebase: powerful history rewriting. Combine commits, delete commits, reorder commits, etc.

- git reflog: unfuck yourself. Move back to where you were even if where you were was destroyed by rebasing or deleting. Git never deletes commits that you've seen within at least the last 50 HEAD changes, and not at all until a GC happens, so you can save yourself quite often.

- git cherry-pick: steal a commit into another branch. Useful for pulling things out of larger changesets.

- git worktree: checkout a different branch into a different folder using the same git repository.

- git fetch: get latest commits and origin HEADs without impacting local braches.

- git push --force-with-lease: force push without overwriting other's changes

Night before flying internationally includes the following checklist:

- check VPN works, can access frontend sites and hit the backend
- git push

Github Inc. (Feel good inc. parody)
=========================

Ha-ha-ha-ha-ha-ha-ha-ha-ha-ha-ha-ha-ha.
Github.
Fetch it, fetch it, fetch it, Github.
Fetch it, fetch it, fetch it, Github.
Fetch it, fetch it, fetch it, Github.
Fetch it, fetch it, fetch it, Github.

Fetch it, fetch it, fetch it, Github.
Fetch it, fetch it, fetch it, Github.

(change) Fetch it (change), Fetch it (change), Fetch it (change), Github
(change) fetch it (change), fetch it (change), fetch it (change), Github

Repos breaking down on pull request
Juniors have to go cause they don't know wack
So while you filling the commits and showing branch trees
You won't get paid cause it's all damn free

You set a new linter and a new phenomenal style
Hoping the new code will make you smile
But all you wanna have is a nice long sleep.
But your screams they'll keep you awake cause you don't get no sleep no.

git-blame, git-blame on this line
What the f*ck is wrong with that
Take it all and recompile
It is taking too lonnng

This code is better. This code is free
Let's clone this repo you and me.
git-blame, git-blame on this line
Is everybody in?

Laughing at the class past, fast CRUD
Testing them up for test cracks.
Star the repos at the start
It's my portfolio falling apart.

Shit, I'm forking in the code of this here.
Compile, breaking up this shit this y*er.
Watch me as I navigate.
Ha-ha-ha-ha-ha-ha.

Yo, this repo is Ghost Town
It's pulled down
With no clowns
You're in the sh*t
Gon' bite the dust
Can't nag with us
With no push
You kill the git

So don't stop, git it, git it, git it
Until you're the maintainers
And watch me criticize you now
Ha-ha-ha-ha-ha.

Break it, break it, break it, Github.
Break it, break it, break it, Github.
Break it, break it, break it, Github.
Break it, break it, break it, Github.

git-blame, git-blame on this line
What the f*ck is wrong with that
Take it all and recompile
It is taking too lonnng

This code is better. This code is free
Let's clone this repo you and me.
git-blame, git-blame on this line
Is everybody in?

Don't stop, shit it, git it.
See how your team updates it
Steady, watch me navigate
Aha-ha-ha-ha-ha.

Don't stop, shit it, git it.
Peep at updates and reconvert it
Steady, watch me git reset now
Aha-ha-ha-ha-ha.

Github.
Push it, push it, push it, Github.
Push it, push it, push it, Github.
Push it, push it, push it, Github.
Push it, push it, push it, Github.

$ git push
> current branch is behind
$ git push -f

... 5mins later coworker is asking why his commits have disappeared.

Last Friday i convinced my boss it was mission critical to have an IntelliJ Idea subscription for my workstation...

I mostly push yaml files to git... 😁 and i regret nothing...

When your internet speed is so fucking slow, you can't even git push 😢

Code with syntax coloring fascinates my young nephew, so after I commit and push, I let him do his thing then later I do a
git reset HEAD --hard

When I first started using Git, I didn't understand the purpose of the 'commit message' and branches.

So I automated the 'git add .', 'git commit -m "update"' and 'git push origin master' so I could update my git repo faster, with one command 😂

Here we go.. 3.. 2.. 1.. F***CCCK!!

`git push origin master --force`

I just tried to "git commint"
And then "gut push"

It's like i have auto correct on my fingers 🙌

git push --force...🔥

My typical development workflow:

$ ssh user@devserver
$ cd /appdir
$ git clone/pull
$ vim file
$ vim another file
$ tail -f /var/log/applog
$ vim file
$ git commit -am 'fixed the glitch'
$ git push origin dev
^D

When there is a conflict, a jedi uses the force!

git push -f 😂

git push --force origin master

*git push*

"There are 27 unresolved merge conflicts"

Developer confession.

I always git push a new branch even though I know it will error as there's no upstream, just to copy the full git push with set upstream arguments from the error message.

Working with the french person in the office and git gets me every time.

shit push, shit merge, shit rebase

Goddamn accent!

To my friends in Ireland, stay safe tomorrow, it's probably going to be nasty storm. Good luck and
1. Git commit
2. git push
3. git out

git add .
git commit -m "hello there!"
git push origin dev-rant

Method 1:
1. Read others' people answers on wk70
2. Apply
3. ???
4. Profit
Method 2:
1. cd <ProjectName>
2. git init
3. dotnet new sln
4. dotnet new console #or webapi/lib
5. code .
6. git commit -m "Initial commit"
7. git remote add origin <github link>
8. git push origin master -u
9. profit

The millisecond after the ENTER you realise you are pushing directly to master. Now you are trying to abort (just did it)

git push origin master --force

Git Push...

Added a mysql-dump file by misstake in a git commit ....

250MB explains why it took so long to push it to the gitlab server ...

a tale of daily frustration:

git fetch
*yup I'm up-to-date ...*
git add -p .
*hack in beautiful patch ...*
git status -bs
*correct branch, didn't forget any files ...*
git diff --cached
*yep, that is what I mean to commit ...*
git commit -m"[TKT-NUM] Meaningful commit message"
git log -p -1
*double-checking ... looks good ...*
git push remote tkt-num-etc

*for a brief moment feel accomplished ...*

*notice typo in commit message ...*

I don't have a funny image or punchline to sum this post up. But know that if you recognise this feeling, then I am your brother in git.

This had me laughing out loud this morning, my wife just looked at me funny as I tried to explain it to her.

Don't forget to git push before reinstalling Windows :)

TL;DR: Fuck.

Longer fuck:
I only did git commit and forgot to push changes. And the rest is pretty obvious.

git push --theLimits

It is time. I have to admit it.

I don't understand Git.

I just memorized some basic commands: git commit, git push, git push -u origin master, git clone, git checkout [-B], git merge. That's it, that's the full list. I use them like they're some kind of magic spells that do what I need. Everything else, those intricacies like rebasing, resetting, HEAD and all that shit, is beyond me.

I'm not a real programmer. Real programmers know Git.

when you're getting mad..
alias yolo='git push --force'

Every time I try to git init ,and push the code to github,
I always forget the cmds to do it!

Every freaking time ,I have to google.

When your peer dev is ++'ing your shit on devRant instead of git pushing the project so you can work on it too 😒 @filipe095

The first push got rejected so I had to use the Windows equivalent sudo command instead

Remember kids, clear out any login credentials before doing git commit and git push!

/smacks himself

Worked whole day from home.
Came today to work, realized i forgot to git push.
fml

When you push and PM (whose understanding of git stretches to git.length == 3) pushes 20 minutes later overwriting all of your changes and refuses to acknowledge their mistake (s).

Now I know for sure that my coworkers can't read error messages.

Every fucking time git doesn't push or pull properly they can't figure out what's going on, almost one year since we migrated to git ... come on... read the fucking message!

My first post is not a rant. This is initial commit. git push -a -muthafaka

Me: How can I delete pushed commits from origin?
Colleague: Just do git reset --hard and then git push -f
Me: But this is dangerous
Colleague: Wait, I'll do it myself
Colleague: Done
Me: But nothing happened
Colleague: Fuck. I just removed all changes on my own branch

Super stressed.
What I did is:
1. git pull --rebase
2. Forgot to build to check if everything is working after pulling new changes
3. git push
4. Now, I realized I forgot to implement a method of the recently changed interface.
It's a production code. Not a joke. And was my first push to prod and I messed it up.
Sad life. Fixing it. Senior Devs must be crazy for my silly mistake.

$ git commit -am "Add drive function and driving_license to class Me"
$ git push

In case of fire:

1. git commit
2. git push
3. leave building

When you leave project without commit and push! 🙈😬

git branch maintenance.

Because certain people like to push to master.

git add .
git commit -m "updates"
git push origin master

"git push -f" be like 🙈

Mom: it's time to go!
Me:
$ git commit -m "I have to go"
$ git push
I'm ready!

thanks to git I get to exercise every day.. I push constantly

Race to git push -u origin master

*doing the happy dance*

🕺💃🕺🎶🕺💃🕺🎶🎶🕺💃🕺

IT WORKS!! It finally WORKS!!! For the first time. AND IT WORKS!!!

```
^s^s^s^s^s^s^s
git add .
git commit -m 'IT WORKS!!!!'
git push origin
git push backup1
git push backup2
```

*continues with the dance*

Worst coding interruption?

The fire alarm going off.
That's when you learn how quickly it's possible to git commit and push

I feel that I'm using
git push --force
too much.

Anybody else feels this way too?

git push -f master

git commit -m "fixed some problems"
git push -f

You know the thing where you put "password":" asd" in a json file to test locally and then push it to the server.

You know when you push to git and not add the generated files to gitignore.

You know when you use "asd123" as salt.

You know when instead of using triggers, you do everything with code.

Yeah...

literally every

`git push --force origin master`

> git push origin master

* [new branch] master -> master

Thank you GitHub.

git add -A
git commit -m "fix bunch of shit.'
git push origin master
**98 files changed

hours later
me: omg I forgot to change the hardcoded IP now it's getting 404

git add -A
git commit --amend
git push origin master --force

Just had a fire at work.
git add, git commit, git push.

No one was hurt. But, the fire was in a server room and the git server is down. At least the halon deployed successfully.

The off site backup should be up in 20 mins. I wonder how often they pull the repo.

Thank god it's Friday, y'all know what what means; git push -f

git push —force

Setup git push notifications (to each of their own channels), together with automatic deployment via webhook, though I'll add notifications to that too, as it currently doesn't have any besides the log file.

Gitea really has been a blast for me to finally get all things git - done, maybe because it is just so lightweight.

Caught a co-worker's gigantic fuck up today – dude totally wiped important code off master with a terrible git rebase + git push.

Gave him the nicest earful I could muster, but I think this is one of those times where I'm allowed to be royally pissed.

Enough is enough! I can't do it anymore!

...

alias pm='python manage.py'
alias ga='git add .'
alias gc='git commit -a'
alias gi='git init && touch .gitignore && printf ".idea \n venv \n node_modules \n out \n *.iml \n *.log \n build \n target" > .gitignore'
alias gp='git push'
alias gps='git push --set-upstream origin master'
alias gr='git remote add origin'

...

Much better :D

git push origin master --force

In case of emergency:

1. git commit
2. git push
3. Leave building

> Failed to push some refs. To prevent you from losing history, non-fast-forward updates were rejected. Merge remote changes before pushing again.

🤦

$ git add .
$ git commit -m "This HAS to be online soon"
$ git push
*merge conflict*
*did not look at difference*
*using mine*
$ git commit -m "resolv merge conflict"
$ git push

$ ssh root@x.x.x.x
# git pull
# cd /path/to/webapp
# npm run production

"Bro, do you even git push?"

Commands, when I make a mistake and you've only got one suggestion. THEN THAT'S CLEARLY WHAT I FUCKING MEANT!

$ git psuh
git: 'psuh' is not a git command. See 'git --help'.

The most similar command is
push
$ git COURSE-THATS-WHAT-I-FUCKING-MEANT

I'm the git expert at my work. This means every time someone has the slightest issue with git (or the git features in their ide), I get interrupted.

😡😡😡

Also I will say it is fascinating watching people who've used centralised version control all their lives struggle with distributed.

"Do you have my changes? I merged them into your branch..."

"You can commit and not push?!"

Guy who thinks git is too much automation:

Files on master:

main.py
main_<other guy>_code.py
main_old_code.py

Also says: Don't push now because I am working on some files and git is not capable of dealing with changes to files within the same time.

WHY?!

git push it to the limit!

Get it?

When you accidentally push an API key to a public git repo :'(

Oh... You're holding my repo up for ransom? Hah you're funny. I'm not paying money for the garbage I haven't touched since...
Also
git push -f

When your ISP forces a refresh of your IP address in the middle of git push... 😕

"git reset --hard HEAD~1" after push

Boss(In company chat): Guys we only need 100 votes to win this award.Do vote and also push your friends and family to vote.
Me: git push -f origin master
Boss: I'll see you tomorrow.
Me: git reset HEAD --hard.

(I think I am gonna get fired)

git push origin master

So I am conducting an introductory seminar on git and GitHub for juniors and as per my knowledge I've drafted this outline, please add your inputs..

The seminar will be of 1 day only

1. Install and configure Git and Github

2. Digital Signature mapping

3. Git init

4. New Project with HTML

5. Configure remote (git remote add <origin> <url>) ends with .git

6. Git commit (git commit –m “Title” –m “commit message”)

7. Pushing git push (git remote push origin master)

8. Git commit –amend

9. Git pull (git pull origin master)

10. Git checkout (git checkout –b new_branch_name)

11. Do some changes

12. Git push new branch (git remote push origin new_branch_name)

13. Git switch branch (git checkout <name_of_existing_branch>)

14. Pull requests

15. Git log (git log –oneline –graph)

When a female developer enters:
git push --force origin master

I'm not sure if diamonds are forever, but Git commit messages after you push, sure as hell are.

-2 mins to weekend, getting ready for a Friday rage push.
Checkout master? Done. Staged everything? Done. Impersonating boss with git credentials? Done.
120 sec to push.
119...
118...
117...

$ git commit - -amend
$ git push -f origin master

git push --force

Because I always push after every commit, when the slightest fuckup happens I just hard reset, commit again, and force push...

...even if it's just a typo in the commit message

Me: Is git male or female?
Friend: male.
Me: why?
Friend: it does all the pushing and pulling!
Me: Really? I think we push and pull into git.

Office door here is perfectly fit:

Pull - when you enter.
Push - when you leave.

Well done boys!

/badhumor

Make a song title or text geeky/dev related, e.g.:

JSON Derulo - Talk Nerdy To Me
Katy Proggy - Firewall
DJ KhaLED - All I Do Is Print
DJ snake_case - Git Push For What

Now you!

In case of Fire

Git Commit
Git Push
Exit Building!

git add greeting.php
git commit -m "added Christmas greeting"
git push origin christmas-tree

Race to 'git push' be like

What can you do with people using so many times git force push ...

* explain gently this is not necessary
* punch him/her everytime you see it
* other stuff that is not in the above list

> be new in a big-ish company
> be working next to a senior dev, who's been working on The Project for 5 months now (15 yrs in company)
> be asked for halp
> senior dev didn't know how to use git push
GIT PUSH
> be Joe's terminally flaccid dick

Push code via FTP, even when GIT was being used for the project.

Why squash commits when you can just --amend the commit and git push -f

#SecretsOfADumpsterFireDeveloper

$ git push --force origin master

Whenever ran into a problem.
Perform git push --force

That is the way to do it...

Our class has a google docs document where we take notes for our technical subjects. I sneaked in a little note about git: "git push -f" is the recommended programm when pushing to origin for a smoothless workflow.

Let's see how many sheeps follow my instructions blindly😈

*fire alarm in dev office*

- git add
- git commit
- git push
- flee to safety

How to get bad co-workers out of your company (if your company uses git and Linux)
Alias push to push --force

Didn't know this will happen anymore. Windows decided to kill itself and is now in bootloop.
The worst: last git push was two days ago

For the ultimate fuckit alias:
alias fuckit='git commit -am "$(curl -s whatthecommit.com/index.txt)"'

gulp && git add . && fuckit && git push && firebase deploy

git push origin ams... backspace, backspace, backspace... master

I didn't manage to win a Hacktoberfest 2020 shirt because I don't use GitHub anymore (and they require that apparently) - but I figured I might as well have a go at it.

echo "- an amazing project" >> README.md
git add devduck.png
git commit -m "update docs"
git push devrant feed

Pls like, comment, share, and subscrieb to CodeWithCondor for moar laif hakz :3

PM: Zip up the prototype and push it to a temporary folder on the master git repo.
Me: *twitch*

`git push origin master --force`

Why does a "senior" developer have a git repo for a critical application that makes our company money, never push to it? I checked it today and it's empty.

An hour of "WHY ISN'T ANYTHING WORKING" followed by ashamedly squashing 20+ local commits and actually remembering to git push the result that time.

Something to cheer you up mid-week:

> alias yolo='git commit -am "DEAL WITH IT" && git push -f origin master'

git push -f

Creating a git repository and forgetting to commit and push. And not only after ending the project or nearly ending the project...

And fucking commenting stuff

I think a "git commit -hide" option could be useful. To hide the author of the commit when you push dirty code.

About to git push -f . May the force be with me

In case of emergency:
git commit
git push
git out

When I'm still a beginner in git, I always use git push origin <branch_name> --force, for the sake of pushing my code on the master branch. My co-worker always complain why the hell there's always conflict on the master branch.

Our company recently moved to git and the number of people who do not understand basic git concepts like commit and push are too damn high! I don' get it, its a completely logical model, what is so hard to understand.

rm -rf *
git add .
git commit -m "Initial commit"
git push -f

git push --force

Make micro level Git commits and push. Don't delete your branch until it goes to prod. Never.

In case of fire🔥:
1. git commit
2. git push
3.🏃‍♂️ Leave the building

Many, many many thanks Atlassian! This is what I wan't to see, when I make simple git push.

Cleaning up after yourself if so damn important. Even your git repos:

# always be pruning
git fetch -p

# delete your merged branches
git branch --merged | grep -v master | xargs -n 1 git branch -d

# purge remote branches that are merged
git branch -r --merged | grep -v master | sed 's/origin\///' | xargs -n 1 git push --delete origin

Do you think the keywords used by git (or other version control systems) are intuitive?

I'm talking to a very junior dev about git and I find myself having to explain around the fact that I don't feel the keywords are great. They are asking good questions like
* Why do you say "push the commit" but then say "make a pull request" - when I want to push why isn't it called a "push request"
* "Why are the metaphors sometimes related to trees (branches), sometimes roads (forks) but you still call it "master" instead of tree trunk or main road?
* Why do you call it "commit", what kind of commitment am I making?

git commit --amend --no-edit
git push -f

git push --force

Hello World! Told my son to press "ok" for all questions. So now, I have to look for backups of projects. Not sure id git push

One hour before demo.
clone,compile and run.
Guess what..?
Most of the key module aren't working
Guess why..?
I forgot to push final changes to git (after pulling an all nighter)

junior be like:

git add
git commit
*wait 0.2 sec*
git push

I still don’t understand git completely ,sometimes the error messages are so hard to understand I just make a new repository and push all my new updates there using GitHub desktop.

TeamWork 1 week before release de projet

Guys i dont know why but all the projet is fuckup in Git ...

Me: where is your firts commit of all these shit ?

He: just there

Me : git reset eb23ae --hard && git push origin HEAD --force

Me: now you sit there and you play with your pencil ! 😡😠

Thx

In case of Cyclone emergency,
git add *
git commit -m "cyclone times"
git push origin master
Run

git push
..
to master

Just posted a comment, and I realise it should be a rant.

In reply to stalkCoder (i think):
| At first there was nothing
| $: git init
| And then there was light

A new creation myth appears.
$ git add --all
$ git commit -m "Update 32 at 2:48 AM"
$ git push
The new creation myth is destroyed by the pure rage of a thousand Git commit message standards.

Yep i love myself