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

Result:

$ wow
$ such commit
$ very push

git everywhere

Git.

The smallest utility made its way to being the largest companies must-have, the most critical part of the whole development landscape.

Using just plain C, Git can shred huge amounts of data insanely fast. It never gets old.

Git is a developer's scalpel.

Git blame strikes again

Solution to all of our Git problems

git blame

Senior dev : * doesn't use git *
Me: you seriously should use git...
Senior dev: * still doesn't use git *
Senior dev: * overwrites production files with old files from other computer *
Senior dev: * talks to boss *
Boss: * gets angry at me *

Me: *just playing around with Git on my terminal*

Friend: "Man, you're such a geek, typing your git command on the terminal.. I myself can't use git without the GUI at all"

Me: *stares at him in silence*

Me: "Wait... THERE 'S A GUI FOR THAT?"

*true story when I was in college*

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?

When AI meets git
- {turnoff.us}

$ git init

git blame
git fired
git depression
git divorce
git homeless
git commit
git job
git house
git wife --better
exit

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

Git blame

The only thing hard about working with Git is working with people who don't know Git

Git newbie

git pull --your-shit-together

Why is the "leave building"command now working?!?!?! Are you sure it's a Git command?? .... Oh shit.

Sometimes I name my project "suicide" so that when I do a git commit I could say that I committed suicide.

Whenever I mistype, "git status" as "git statsu", I thought I was speaking Japanese. 😂

No, I'm not "switching to FTP," it's about time your learn git mate.

Toughest part of git is writing the commit message

Wtf?? Who wrote this shitty code???

* git blame *

Oh... Right... It was me...

I love when I accidentally write "git ass" instead of "git add". I laugh every time.

Xkcd's epic rant on git. How deep have you explored git internals?

Giving instructions to Git and ending with

"Did you Git it?"

Git merge <3

Why the fuck did I set up GitHub and all the deploy scripts if your just going to fucking ignore it and edit directly on the server?!?
"Oh, I ran out of time"
DO YOU EVEN KNOW HOW SIMPLE GIT IS?!?!?
"git add file
git commit -m 'Queef farm'"
AND YOU'RE DONE!

May I introduce you to my coworkers git repo

"Git pull a day keep the conflicts away"

Git log went wrong 😰

For the last time, git is not GitHub.

Git commit -m "nothing to say"

You know you messed Git hard when your commit graph started to look like November Rain on Guitar Hero.

The superpower to perform version control on reality. (Git)

Imagine this universe (the current branch), which is made up of a series of events (commits).

Having this ability to allows us to:

- undo events (git reset/git revert)
- reorder events (git rebase)
- transfer to another universe (git checkout)
- derive a new universe from current universe (git checkout -b)
- delete a universe (git branch -D)
- apply an event from another universe (git cherry-pick)

and my favorite:
- merge universes and their events (git merge)

we have to resolve conflicting events, of course.

What else? ;)

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

Gotta admit, I'm still finding out this git thingy.

😅

my thoughts on git

Got my head detached today...

Good thing a simple git checkout solved it

I forced my friends to use git(hub) as vcs because their project was in a usb-to-usb state, which was unacceptable for me. So I offered them my help and uploaded it (with a little bit of a forced consent) to github, to end this misery. Of course I helped them the basics of git. Now they automatically use git(hub) as vcs and to share their code.

I feel proud for this :)

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

Git for pros only...
Credits: javascript.js

git merge

A poem for git in git

git happens ¯\_(ツ)_/¯

What does a Git say to another?

Check this out man

Every normal developer:
git pull

Me:
gti pull
gut pull
gi pull
git pill

Goddamn

Fuck git!
Oh, it's solved.
I love git! Git is awesome.

"Who the fuck wrote this stupid shit!?"
git blame

It was me...

What I've learnt so far using git for the first time in a major project.

Git commit Suicide

Learn git before anything else...

Git...

Git...

I "Git Pushed" my friend to "git commit" with a girl he likes for long time

But now my other friend wants to "git rebase" on top of her ....WTF

Now need to resolve this merge conflict 😂😂😂

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!

I wish i could git reset --hard my life

Everyone in my company prefers solving git issues rather than `rm -rf` & `git clone`

Feels like I'm working with a team of geniuses. 😂

Friend: Check out that hot chick over there
Me: git checkout -b hot-chick

#foreveralone

Using a git GUI is like dulling a sharp knife in fear of cutting yourself.

git music

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

> 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

I just started using git. it is unbelievably useful. What an idiot I was that I didn't start using it earlier. I LOVE GIT!

alias "git commit"="git reset --hard HEAD"

A Day in git

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

My git commits are mostly "did shit and stuff" or "changes by David Bowie"....

Git!=Github

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

Every time I mess up my git branch I usually find that its pretty futile to fix it with fancy commands like 'git reset', 'git prune', 'git rebase', etc. I usually find it easier to just start over from scratch.

They should really add a command for that

'git fuck-it-start-over'

git commit -m 'fixed the issue with my light switch'

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

My favorite git commit messages:
- "Changed Something"
- "Fixing Something"
- "asda"

Probably posted before, still funny!

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

Sometimes I forget that not all Terminal commands begin with "git."

git ls
git less fileName.ext
git cd ..

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*

Some days you get git, other days git gets you.

!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

git commit -m "last"
git commit -m "last1"
git commit -m "real last"
git commit -m "real last 1"
git commit -m "real real last"

I just wrote "git vomit" instead of "git commit".

Night before flying internationally includes the following checklist:

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

I forced myself to use git on my latest projects. And the more I use it, the more I love it. I can relate to all the git-love here on devRant.

Fb Source: is it git or jit?

Me: whyyyyyyy would you start this?!

git add .
git commit -m "all the changes I did in 20 years"

That's how I roll

My coworker enlightened me with git stash. Just :woah:

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 😂

One day Linus Torvalds will make a statement about git like: "Why is everybody using this? It was just a joke!"

I forgot to git fetch, so I spent quite a while doing exactly WHAT MY TEAMMATE HAD DONE JUST HOURS AGO

Typed "git" instead of "get" twice this morning

To all those people that have Git alliases like:
"gc" = "git clone" or "ga" = "git add"

What do you do with all that extra saved time?

My IT leads git commit history. Lol

Git is life

A git commit message ending with a question mark probably contains questionable code.

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.

the shortest horror story:
git merge

Learning git

Wanna gently annoy your coworker? Every time they send you an idea about something code related, just respond with:

"git checkout shitty_ideas"

git stash is ❤️

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

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

/smacks himself

git reflog, git reflog...git FUCKING reflog!!!! Ah fuck this, I'm taking the kids out. 3hrs later.... Oh shit, i was in the wrong directory. A good fresh air clears the mind.

$ git reset --hard life

I finally learned how to use git, and now I'm in love with it

First git commit readme.

Exactly my feelings when I switch between TFS and Git

git add -all
Error: did you mean '--all' (with two dashes ?)

Every.
Fucking.
Time.

When you git blame a crap line of code and find out it was your commit

Race to git push -u origin master

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

Anybody else feels this way too?

git push origin master --force

If see another "n case of fire..." (git) post...

Commiting Prod credentials to git.

new git alias :
mergetool : rm -rf .
just delete all conflicts in code

Self-storage seems very git hub inspired 😂

git: 'fucked' is not a git command. See 'git --help'.

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

Friday. 17:56. Time to go home.

> git add *
> git commit -m 'wip, feature almost done, need to test'
> git pu... [BIG FAT BSOD]

fuck it, I'm out

Lead messed up the Git workflow (New repo), ask me to fix it. And when I said that we better do it from first properly, asked me if I even know git 🙄 Feel insulted.

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

One of my teachers pronounces the 'g' in 'git' like the 'j' in 'jet' and it confuses me each time he says it

$ 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

I freaking love git.

That's all.

PM asks me how to use git. 😑

Binary searching my way through the git history to find the commit that broke something. 😄

Accidentally rm -rf a git repo, one of the branch still not pushed to remote yet. I managed to use file recovery software to recover the .git folder, any idea what to do next?

When unicorn goes down during git-merge conference!

Falling in love with Git !

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)

Dear git,

FUCK YOUR FUCKING FUCK SHIT .GITIGNORE FILE! WHY CAN'T YOU JUST FUCKING REMOVE THE IGNORED FILES FROM THE VCS? EVEN GIT RM --CACHED --FORCE DOES NOT WORK WTF

TL;DR
"git" your shit done.

Yours sincerely
Scrumplex

Am i doing it right?
git commit -m "Multiple changes and minor changes in the project."

I don't know git

Sometimes I think that git is like a drug. After getting past the initial learning curve, you use it in every single one of your projects. Sometimes I wonder how have I ever survived without git before.

just another day in the Git pull room

git blame

Race to 'git push' be like

*fire alarm in dev office*

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

trying to auto complete git commands be like: git checkout f..TAB...TAB...WTF!

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

This is what Git Branches look like while working with an awesome team

Use “git commit —amend” the 1st time. The mark of men

I think of git as if it was my dog. For added fun name your remote "slippers". Then you can exec "git fetch slippers"

alias suicide = git reset --hard

Honestly, without git version control I wouldn't know how I could manage my project properly. Git is awesome in so many aspects <3

Me: we should take this project a little more serious, follow the coding standards and please let us use git!

Pal: Oh sure.

//made a new repo and the first commit, sent the link and prepared everything (Granted access etc.)
//2 weeks later

Me: What's up, I already got quite some commits and you haven't pushed anything so far.

Pal: Pushed? what do you mean?

Me: I'm the talking about the git repo, I'm the only one contributing.

Pal: Oh yeah git, I installed it but I have no idea how that stuff works. I opened Git gui but i don't know what I'm supposed to do. I got everything in the Dropbox tho.

Me: ... ... ... FUUUUUUUUU WHAT THE FUCK MATE ARE YOU SHITTING ME, THE HELL DO WE HAVE GOOGLE FOR AND WHY DIDNT YOU ASK, LIKE WTF SERIOUSLY I EXPLICITLY TOLD YOU TO USE GIT.

😣

I lost a week's worth of work due a git conflict, please kill me now.

Every other day, Git is the best version control ever. Today, got damn it Git, why can't it just work

Git: the occasionally frustrating, dangerous, and infuriating VCS you can't believe you were living without.

Fuck me and fuck merges and fuck conflicts!!!

I still love you Git but sometimes you are a harsh mistress.

I think the reason why git beginners have a hard time with it is because the api is a bit untuitive.

For example: if you want to "unstage" staged changes, you run git reset, and if you want to "delete" those changes from your working copy, you git checkout those files.

But then, you find out that you can do all of that if you git add . and git reset --hard.
So you're like "huh..."

And then you discover that if you end the resethard with a branch name/commit id then you also make current branch point to the commit or that branch/commit (respectively).
So you're like "huh..."

And also if you add a commit id or branch name to git checkout, you change the current branch to specified/enter detached state with HEAD pointing to that commit (respectively).

Oh and you don't use git branch to create branches, you use git checkout -b because it's a lot shorter.

So here's a rundown: git reset mutates things related to files, but also mutates things related to branches.
git checkout also mutates things related to files and mutates things related to branches too (in a diff way). Also, creates new branches.

I don't think this is intuitive. We users use the same commands for different purposes with just a different flag.
Commands shouldn't mutate different types of things. But don't composite commands (as in, "smart" commands that mutate different things) shoudln't be a flag in an existing command, it should be a single new command of its own.

Maybe if I reread the internals of git now, I'll be able to disgest the dozens of technical terms they throw at you (they are many). And in my mind, the api will cognitively fit to the explanations.

Here's another one that feels weird too.
If you want to make your changes start on top of someone else's commit, you do git rebase.
But git rebase -i can be used for that, and also to delete, modify changes or message of, reorder or combine previous commits of the current branch.

Maybe the reason why several things we do overlap with the same commands is because they internally do similar things, and while not separating those commands might make it less intuitive, it makes them more sensible? i dunno...

disclaimer: I'm not setting this opinion in stone though, and am aware that git was created by one of the most infuential programmers.

Turns out deleting a git branch also deletes your unchanged changes fuckkkkk

Well as good a time as any to learn how to use 'git fsck' and manually sort through hundreds of dangling blobs

FML

In case of emergency:
git commit
git push
git out

Never `git rebase` when you get home from the pub....

`git push origin master --force`

Im rubbish at git, everyday I end up ruining my repo and have to start fresh

my company uses svn for source control. just found out the guy in charge of the repo actually uses git and just has all developers use svn because "there's less of a learning curve". WHY?!?! Git is so much better!

Git takes a while to git git, but when you git git you git git.

One day i started to code.

One day i was told you will not code without git.

Many days i lost code on git because i was ignorant.

Today i reset the act of commiting without losing all my shit.

Git reset --soft HEAD^

I didnt event sweat it ;)

Today i feel like half a boss!!!

How hard is it to make a git GUI that is 1) pretty 2) not sluggish 3) bug-free?

Pro of not using Git

* No git conflict

git push --force

Something to cheer you up mid-week:

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

Dear git, why are you lying, there's no changes in that file, you say that yourself...

What's your favourite git client and why?

git blame...

I might have asked this before, but since everyone on devRant except me is familiar with Git, please help me out a bit.
1. Should I use Git for a personal (game) project with a friend? (We'll work together via skype since we live far away from each other)
2. Noobs call Git "too difficult" - it seems difficult to me as well, what's your best advice (or resources, Git alternatives) to pick it up easily?
3. Will I have trouble with my slow internet (4mbps down 0.2mbps up)?

Learn git, Learn life! 😊

junior be like:

git add
git commit
*wait 0.2 sec*
git push

Is it just me or "git blame" is just the best feature of git?

Interviewer: Can you rate 0-10 your git skill?

Best git commit messages ever(sarcasm):
- Fixes.
- Changes.
😥

Git to the rescue

Sometimes git reflog saves your day.

Why is there `git stash pop` but no `git stash rock`? Come on, man!

Wondering how many people use git cmd and how many use different git clients.

I regularly use git cmd. I made a transition from clients a while back because I wanted to learn more about how it actually works and it works just fine for me, except when I have to google something I don't remember (like how to revert local commit)

Git clients will for sure do abstraction which can be both good and bad, but I'm wondering if there are any definitive pros for clients.

its funny because Git is the fkin master lol

Last comment of git commit: "it works"

I love git stash.

It's helps a lot for doing refactors to me. I guess it's not the most complex workflow, but it wasn't obvious to me when I started with git. Let me explain.

Refactors. As you start writing the first lines of a refactor, you start to notice something: you're changing too many things, your next commit is going to be huge.

That tends to be the very nature of refactors, they usually affect different parts of code.

So, there you are, with a shitload changes, and you figure "hey, I have a better idea, let me first do a smaller cohesive commit (let's call it subcommit) that changes a smaller specific thing, and then I'll continue with the upper parts of the refactor".

Good idea, but you have a shitload of changes nearly touching every file in your working copy, what do you do with these changes? You git stash them.

Let's say you stash and try to do that smaller "subcommit". What sometimes happens to me at this point is that I notice that I could do an even smaller change inside this current "subcommit". So I do the same thing, I git stash and I work on that even smaller thing.

At some point I end up `git stash pop`ing up all these levels. And it it shows that git stash is powerful for this.

* You never lose a single bit of work you did.
* Every commit is clean.
* After every commit you can run tests (automated or manual) to see shit is still working.
* If you don't like some changes that you had git stashed, you can just erase them with git reset --hard.
* If a change overlaps between a stash you're applying and the last "subcommit", then
if they differ, git shows conflicts on the files,
if they are identical, nothing happens.

with this workflow things just flow and you don't need to wipe out all your changes when doing simpler things,
and you don't need to go around creating new branches with temp commits (which results in bloated temp commits and the work of switching branches).

After you finish the refactor, you can decide to squash things with git rebase.

(Note: I don't use git stash pop, because it annoys the fuck out of me when I pop and you I get conflicts, I rather apply and drop)

The moment when your git commit date is in the future because git uses your wrong system time

Me everytime on git

git checkout origin/develop
git status
You are not currently on a branch.

Only computers and nerds can argue like that.
Expected behavior: I'm on branch develop, but nevermind, let's overcomplicate everything.

For the first time in my life I removed a wrong commit with git rebase and I did not made a mess.

More then 10 years of using git and keep learning.

git log .. I see what you did there

When the fire alarm at your company goes off and instead of saving your life or thinking about your family your first thought is

git commit
git push

...

I keep typing `git stash poop` … am thinking of creating an alias for it

Is git source code versioned on git ?

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

So I started using git submodules. It seems I've walked into something unexpectedly cumbersome.