"Don't use git, it is too complicated and we don't have time for this."

2 days later the same person made changes directly on the FTP which I later unknowingly overwrote.
Take that you imbecile!

CEO: You need to use git.
Designer: No

CEO: You can backup stuff.
Designer: No

CEO: You don't have to save copies!
Designer: No

CEO: You will use a really cool command line!
Designer: No

CEO: It has unlimited storage
Designer: So when we start?

Told us to use facebook or google drive to share code instead of git

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*

"We don't need Git, just use e-mail!"

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?

Governments should use a public git for their laws

Me: I use Git!

Classmates: what's that? A Softdrink?

Me: Nevermind. Just Copy the source code on gooogle drive.

Classmates: Thanks!

Me: -_-

Git makes it easy to search through historical changes they said. Git is amazing when working in teams they said.

It sure is.

If your coworkers do not commit every time they burp or fart, do not use "🚀" or "✨" or "fix" as a commit message, and do not push all their shitty experimental broken branches without cleaning up.

I'm surprised there are no piles of fecal matter behind their desk chairs.

When you suggest to use git but the answer you get is:
"Just write in a text document what you have changed ".

Oh dear God..

My collegue:

- Is it file.php or file_new.php that are in use?

If you could take the time to learn git then we wouldn't have these questions all the time.

We're in 2017 and some people still wants to use Google drive instead of Git :(

My girlfriend keeps dropping hints that I should commit, but I still haven't gotten around to learning to use git.

So I've been working with this "developer" on a client project and she is still refusing to use GIT.....

My first step to a better 2017:
Learning to use git.

A couple of weeks back, I met some of the kids from my old school. They had joined together to form a small team and were designing and deploying websites for local businesses.

Turns out that they were mailing each other and using Dropbox to manage the source code. This had been going on nearly for an year.

I spent a couple of hours showing them how to use git and gitlab. Basics on committing, pushing, pulling, branching and merging.

I will never forget the look on their faces! They had seen God and its name is Git.

Me 3 years ago watching someone use git on terminal: woaah is he a hacker???

Me now: *types git status, press enter* *repeat 3 times*
Non Programmer friend: cool! are you hacking?
Me: Nope. Just forgot what I was trying to do

*Overhearding Convos*

A : "Dude, have you tried vim? It sucks!"

B: "I know right, why do they have to make it so hard to use..."

Me whispering : Git Gud Boi...

Begin a lazy fuck -> not taking the time to learn git while I've had plenty of time and now I still hardly know how to use it.

Being able to use git on my life.

other dev at work: "why cant i switch branch of my SVN repo like Git"
Me: "Cuz it uses different approach, different branches are at different locations......."
Him: "but how can i use it like Git"
Me: "you cant"
Him: "but why"
Me: "Get away from me before i throw something heavy at you"

Git Pull Failed, Merge Conflict.

Me:
don't do it
don't do it
don't do it
don't do it
don't do it
don't do it
don't do it

Me:
Delete local project folder and pull the project down again.

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 :)

Project Leader: the team needs to use Git
Dev team: yeah Git, it will help us a lot
.
.
.
[three days later]
Dev: we send the changes via Dropbox, see you on monday!

Don't use git

Professor refers to Linus Torvalds as the most arrogant developer. Says no one uses Git and thinks it has no advantages over SVN. Forces us to use SVN. :'(

Me: So how do you handle conflict
Candidate: I use git kraken to highlight my conflicts and walk through them one by one

Probably the most developer answer i've ever heard hahaha

*my first day on the job to work on a website used by dozens of companies worldwide and 1000s of users*

me: So where can I find the git repository?
dev: Git?
me: Uh... what kind of source control do you use?
dev: We don't use anything fancy like that.
me: *freaking out a little, I already committed to this job*
me: So then where do you edit your code and how do you back it up?
dev: Oh, I just edit it on FTP and zip all the code every week.

I'm not angry, mostly sad.

At my workplace we don't use git.
There are constant overwriting, sending code via email or USB stick and forgetting passwords to zip-files shenanigans going on.

I already use git for all my local projects (literally git init in the directory) but my coworker and I thought that it would be a great idea to have a local server with a Gitlab running on it.
So I started looking into running a self-hosted Gitlab (for about 15 minutes) and then our boss who was sitting right next to me almost shouted at us: "Such stuff should be coordinated with the boss! We don't just do something and burn my money because it's _cool_!"

No, git is not cool, it's necessary for crying out loud! Gitlab is cool but at the end of the day also just another tool too.

I guess I have some persuasion to do.

I don't know what version control has done to our boss that he has such a deep dislike for it.

My professor once asked us to brainstorm a good topic for our IT seminar/workshop.

I suggested version control using Git.

She simply shrugged it off. She said she needed a topic that the class can use. WTF.

do we have to use git/version control software? why cant we just mail everyone else the builds at the end of the day?

Often saying fuck it when I've got a project and I kind of really need to use git but I'm not good with it so I just go back to good old scp again 😅

I'm a simple man, I want to:
- get along with everybody
- be able to depend on my coworkers
- use whatever editor I want
- have vcs (preferably git)
- listen to music while coding
- work with people who share my hobbies (optional)

Had a fun little conversation with a potential employer...

Him: We use git for version control. To work with our team you'll be expected to do the same and be proficient at it.

Me: Not a problem. I am well versed with all things git! May I ask, what does your work flow look like?

Him: All of our source lives in a single repo and everyone commits straight to master.

Me: 😐...

Him: Conflicts will not be tolerated.

The importance of version control. Had a school project at a real company and i didn't understand it so i said fuck it. Then someone asked me to alter the js library a little and push/pull that to the server. I thought fuck it, altered it and accidentally pressed save (automatic ftp upload). Suddenly the file was overwritten (that guy worked on it for 6 fucking hours) and it went from like a thousand lines to just a few. We did restore it from the browser. He said: either you're going to use git or you're out.

Then i started using git.

"Gitard' - a programmer struggling to use git commands to control their source code repositories.

Still not learning git properly. I still find it very hard to grasp how this works and although I'm starting to use it more and more, I just can't wrap my hear around it so I often reside to scp for upload and no version control at all.

:'(

introducing my classmates to git and how it can help us.

*explaining scm, git, github and bitbucket, and conflict resolving*

"why don't we just use google drive ?"

Your first day at work be like:
"If your new team doesn’t use git, announce your resignation immediately and walk out."

Friend: I don’t need git. Git is for people like you who cant do good backup of their code
Me: Yeah, yeah, go do whatever you like...

2h later comes to me:

Friend: Can you make me repo and show how to use it...?
Me: What..? You drunk?
Friend: Naaah, no... My disk broke while ago...

Karma is a bitch :D

Wasted 45mins interviewing a "developer" who couldn't use git, the command line, CSS preprocessors or task runners. His sites were all template rubbish and he wanted £300($370) per day.

A colleague from university cried the last week that he cannot use git. For him it was just a big pile of software BS. I didn't bother to ask, as he is a very whiney person and complains about everything.

I asked him today...

He tried to create a git repostitory on his usbdrive. How else could he work on different machines???🤔😝

I tried to introduced him to Github/Bitbucket/...
He knew about them but was afraid they would sell/use his bugriddeld programming excercises😂

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

This is a small project, I don't need to use git on it...

ALWAYS use VCS.

I have a confession to make....

I just started to use git two days ago.
But atleast I GPG sign my commits

!rant

I just wanted to tell you guys:
That after a month or so working on a spaghetti pile of codes, our team finally decided to study and use Git for our project.

I'm so happy right now 🎉

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

Working on a group project for uni and this dude asks me "why would you ever use github instead of google drive?" because git gud you cunt

One of my classmates asked me why we should use git, if we can put the eclipse workspace into Dropbox...

*FourWeeks From Deadline*

Two CoWorkers: "Oh cool, Visual Studio 2017 is out, I am gonna switch"

Breaks the build.

They then tried to spend hours trying to get the project to work on both versions, with no success, then let us know.

I am just glad we use Git

Use git or get hit

Photoshop,...

because why use an:

IDE / editor,
terminal,
SASS/LESS compiler,
package managers,
git,...

when you can make your website as a photo, slice it up and export to html. EASY PEAZY

I just got hired as a systems administrator at a company that develops web forms. NO ONE in the company has heard of git. They don't use any kind of version control.
I'm a little worried...

Before knowing how to use git: Pff, it's ridiculous...
After knowing how to use git: *modifies 3 lines*
*git commit*

What's your favorite shell alias that you made for yourself?

I use this one all the time:

squash () {
git rebase -i HEAD~${1}
}

Runner up though is `git-fuckit` which resets everything to origin/master.

!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

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.

The use of git and understanding/working with foreign keys and performing (including the understanding) JOIN queries.

Also, it took me years and to understand OOP.

When think back to my code from before that, my brain spontaneously starts bleeding.

Apparently my classmates are open source enthusiasts and know nothing about how to use git.

How many of you use GIT from a plugin in the IDE?.
I've never even tried to use it.
I feel that cli is the way to work with git.

Some of my coworkers call connecting with SSH "git bashing", because they use git bash for making ssh connections. 😋
They never understand me when I use the term "SSH". 😔

God bless the Git, for the has done the forsaken and deleted a script many a era ago, and on this blessed day of days, he who is a dickhead needed such thy script to test functionality thy requires to be in the heavenly clouds to utilise....

Fuck I love git history to save me from having to write this thing again 🥰

Ps: IF YOU DON'T USE GIT, BE ASHAMED!

When you teach someone to use git and all.of a sudden you are required to supply all the answers when they run into problems:/

I tried to point them to Google and they still keep coming back. Why the fuck did I do this to myself?

Anyone else have to deal with an asshole who refuses to use the git repo? Not sure how much longer I can hold onto my sanity.

Countless times. Here is two:
- when he said he prefers an external hdd over git
- when he said that git is just a shiny new thing, we young devs use just because it's new
- etc

Poll: How do you use git?
Command line?
GitHub Desktop?
3rd party app? (which one)

I use command line almost exclusively.

Why the fuck someone write "used linux to speed up development" in your resume. But when you have to use it, questions like "where to download git for linux?" appears?

```
Your branch is behind 'origin/master' by 562 commits, and can be fast-forwarded.
(use "git pull" to update your local branch)
```

`$ git pull`

```
251 files changed, 103274 insertions(+), 1361 deletions(-)
```
okay fuck.

Another real-world argument for why I always say git is worth learning properly.

Had to track a really weird bug down today. Had no idea where it came from, how long it'd been in the code and hadn't the foggiest what was causing it. Realistically it could have been introduced any time in the last year or two, and that's tens of thousands of commits in this repo.

Git to the rescue. Knocked up a quick script to test the case in question, fed it into "git bisect run", and 30 seconds later git found the exact (small) commit that caused the issue.

It's a brilliant part of git, yet it seems like almost no-one I know uses it. Some use "git bisect", but using "git bisect run" and passing a script to it seems to be alien to most - yet it's probably my most used tool when it comes to tracking down bugs like these.

Was forced to code like this:

if(condition)
{
//code
}

Instead of this

if(condition){
//code
}

Also I should mention that this happened 4 years ago and my mentor (27 years old economy major at the time) did not know how to use git, we stored projects on a shared networking folder.

I'm in internship, why the fuck am I the one explaining them how to use git, Android studio????? Why am I the project manager?????? I'm supposed to learn from you not the opposite. Fuck this monkey.

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.

Why don't designers use git, or at least use version numbers in their files?

Looking at around 20 files in my downloads folder called "final" and it's bloody annoying.

My new start training at my current place of work.
Learned how to use Linux, terminal, ssh, git, MySQL, how to create basic web apps with Spring, how to write unit tests and UI tests. All in the space of 4 weeks. Best training I have ever been on.

I don't get it when people (developers) complain that git is hard and unintuitive to use.

Most of these people use some GUI client to do the dirty work. I've found every Git GUI client that I've tried tedious.

Does anyone relate?

After having to use Git and Bitbucket for over 2 semestres, my teachers decided to give us a Git tutorial where the whole class had to work in the same class. This was the result.

We work with about 7 developers at this company with 80 somewhat websites in production.

We edit changes directly trough FTP and we use ctrl+z as version control...

(yes since i started working here I've been demanding git, I'm spearheading it and we are getting there slowly)

Working with guy, who don't know how to use git ☺️🔫

Document your code, Don't give your variables silly names. Use git !!

somebody must have told don't use dropbox use git

Ok so I was talking to my computer science teacher earlier and he said that he would rather use vim over PHPStorm for creating a laravel project. WTF!

Normally I would be cool with it, but he has pushed faulty code to git over 8 times. I'm just done.

boss: wish there was a way to go back to older versions..
me: there is, it's called git, I can show you how to use it!
boss: nah we will just keep using the sync on Dreamweaver
me:....the fuck?!

Me when I finally get my client to move away from shared hosting to a vds and being able to use git on the server.

I'm a software developer. Last week I spent half a day teaching a "Senior Data Scientist" how to use git branches. I spent the other half a day teaching him how to use Jira. Now I'm being told that the dev team isn't raising enough Pull Requests. FML

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

TL;DR : do we need a read-only git proxy

Guys, I just thought about something and this potential gitpocalypse.

There is no doubt anymore that regardless of Microsoft's decisions about Github, some projects will or already have migrated to the competition.

I'm thinking : some projects use the git link to fetch the code. If a dependency gets migrated, it won't be updated anymore, or worse, if the previous repo gets deleted, it can break the project.

Hence my idea : create some repository facade to any public git repository (regardless of their actual location).
Instead of using github.com/any/thing.git, we could use opensourcegit.com/any/thing.git. (fake url for the sake of the example).
It would redirect to the right repository (for public read only), and the owner could change the location of the actual repository in case of a migration.

What do you think ? If I get enough ++'s, I'll create a git repo about this.

At my first job I had a senior who took backups of code by zipping it and uploading on Google drive. Once I told him why don't you use git, he said it's not as secured as Google.
I left the job one month later

I think what would help is to teach them these things:
- awareness for security in code
- how to use a fucking VCS like Git and how it works

My team is using Teams to share code snippets. And because I know they don't (know how to?) use git remotes, I have to share my code through Teams as well.

How can people use git like that ?
Paris' metro has a simpler network.
If you can stop yourself from all working on the same branch at least do `pull --rebase`.

Does git use git for it's development and version control? 🤔

My company’s code base is so messy that the dev branch and master branch is so buggy. But they put the blame on me as usual.

I use git blame, I wasn’t the author .

I once thought about tweaking the JS files and replacing ";" with a similar Unicode character just to teach a lesson to the guy that refuses to use Git.

Me talking to a friend

Me: Come on, you should use git, it was even created by Linus

Friend: Who’s Linus?

Me: *Wanting to be the one found by Logan Paul*

I've introduced git and github to my class, the teacher said that I gave him a good idea for a task that everyone would have to use this... Now I think everyone hates me Xd

Best git UI for Linux? Or should I grow more chest hair and use the command line?

Do you use Git with GUI or CLi?

Do you guys use git?GUI or terminal?why?

The more i use git.. more the fun it is.. Just found out the usage of rebase and cherry-pick.. I have read about the implications of these commands in a shared repo.. But it is fun to use it in a solo repo..

I’ve started at a new place - the team use Trello to share code 😳They are happy to zip a folder, upload and download each time a project is updated.

I’ve tried to sell the benefits of Git however some have such conviction that it would be worse. FML.

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?

- Learn go
- Learn how to properly use git
- Release my first (useful) app

My colleague does not use git (well, not for much), hates all external frameworks, and when he sees my code he tells me "that's not how I would have done this", every single goddamn time. Aaand we are the only two developers in our company.

PM asks me how to use git. 😑

Why the hell do I have to keep showing everyone on my team how to use git. Learn it God dammit!!! Is not that hard. How come you freak out on a simple conflict? Why don't you delete your fucking merged branches?

I had to migrate ~100+ svn repos to git that were "useful" according to the client but found out that there were a lot of projects (+6yrs old) with only one commit message "--no-commit-message" and i'm not even joking...
And then I had to explain to these "devs" how to use fucking git with eclipse (+they all use light theme...) cos' terminal or gui client is too complicated

And then I saw their "Java libs" with ~3k line of spaghetti

Do you even dev bro?

-use git
-use dark themes
-drink cofee

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.

[on git] "how can I use the remote to see what's on my local computer? How do I know if someone else has cloned so I don't edit their files?"

By itself, not terribly stupid... Git can be complicated... But this is coming from people who are supposed to be familiar with basic CM, but aren't.

Just got an email from the boss asking if me and the other dev on a project have been liaising with each other before editing code because changes were being lost and over written.

Wouldn't it be great if here were some way to manage collaborations and control versions of files? *git*

The company is so reluctant to use git and do things properly.

-.-

Started a new job and our tech lead doesn't know how to use GIT in a team environment, has only ever used it while working by himself on one person projects. Kinda worried...

"let's use git for this game jam"

Wait! Don't go! I love git and use it on every project I work on! You'll have to hear me out here.

This was 4 years ago, at my first Global Game Jam. Every jam and game I'd worked on up to that point, I was the only Dev; no need for git, as backups were more than enough. I joined a group with high hopes for the game jam, with three coders and a proper art team.

The entire jam was "1 step forward 2 steps back", as git somehow constantly overwrote code as fast as we could write it.

By the end of the jam we barely had anything to show for our hard work. The takeaway isn't even about git. It's simply to never work with other people. Git is a great protocol but it can't stop people from accidentally fucking other people over. Every jam since, I've worked on my own and had a far better time of it.

Doing a project with someone and find out that they don't know how to use GIT. He copied the file he worked on, put it somewhere else (using the Github uploader) and wanted me to merge it with the original.

When you use a git command you don't really understand and it fucks up your day!!!!!!!

> 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

Freelancer/coworker: "Why don't you just use source tree instead of git in the command line?"... me: *face palm*

It saddens me that comp sci teachers at my school don't know how to use git and stackoverflow

Even if you are solo, use version control and commit often. When you are working on something completely new, git reset --hard can really get you out of a bind.

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

From a Dev at my old place: Don't use git for such a small project, I think we should use email to send our code to each other.
Turned out that this "small project" was a piece for a larger project.

Also turns out there's such a thing as merge conflicts outside of git.
Our code was broken for 3 days once because of his shitty advice.

phpMyAdmin

Well, it is not my favorite open source project... I almost never have to use DBs, but when I do, it just saves my life. I can create the tables, keys without worring about any SQL command.

But day to day life is GNU/Linux, Firefox, bash/zsh, git... There are lots of opensource tools that I use, and love, everyday. :)

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.

😣

Waking up to another day of being forced to use SVN because my university seems to have a problem with using git. Who the fuck uses SVN now anyway, piece of shit version control.

I had a collage who kept linux commands like ls -l, ssh and git commit/pull/push in .txt file and when he needed to use them, he just copy from the file and paste them to command line EVERY F*CKING TIME. He just didn't won't to learn them.

Merge VS Rebase:
- Did you pick a side?
- Practical tips? Like dealing with merge conflicts
- Have you ever regretted using either?

My answer
* My team squash-merges all branches to master so we don't really care what the branch history looks like. Master history should be pretty - but a branch history can be ugly and filled with a dozen commits.
* Practical tip 1: use `git config rerere.enabled true`. rerere stands for "reuse recorded resolution" and this means if you rebase often you don't have to resolve the same merge conflict twice.
* Practical tip 2: use `git commit --fixup oldcommithash` and then rebase with `--autosquash`
* I like using Rebase. But I have regretted the amount of time I've spent on trying to rebase old branches with many commits only to give up and to `git rebase --abort` since I realised I couldn't handle trying to reapply all the commits chronogically as the changes in the 1st commit were no longer relevant.

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

I know it's not recommended to write git commit messages in past tense, but it makes more sense to me to use it. Maybe I'll change as I grow and learn more in the programmer world, but as for now, I'm going to be a rebel and ignore convention😎

If Microsoft acquires GitHub, it will be far from the end of git. Even if it is an EEE play, there are still many FOSS variants that will enable the use of git without having to deal with Microsoft's toxic business model.

I still have my gitlab install, and I will continue to use it.

Git vs floobits

I hate floobits! But my team wanna use it because they are too lazy to commit their code!!!

Is it a good idea to use Github or have a private local Git Server? I’ve heard Github now let’s people make private repositories for free so I was thinking of that but idk. What do you guys use?

What’s happening to devrant the other day I saw a post how ppl preferred git gui over cli, just now saw a post where light theme ppl united. Where is my elitist crew?

I use arch btw /s

As a Dev in college working for teams in college, I don't really have a need to use git, since most of 'self proclaimed prestigious programmer child prodigies' I work with have no idea what it is; but I use it anyways as good programming practice and ease of backups.

So I tried using a GUI client after months of the git bash, and even though I looked up a few tutorials (was embarrassed the whole fucking time). I ended up adding, committing and pushing via bash.

Can anyone explain me how is the GUI client helpful in large projects and stuff?

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.

Use names for variables which describe what you store in them, writr comments and always git!!

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

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!

Well since vim & git has already been said gpg. you can use it as ssh keys and sign your commits to make sure nothing nasty is added to a git repo under your name

At one point I understood a lot of git internals. Now I don't remember shit apart from the small subset of commands that I use everyday.
How does one remember such intricacies.
Also same with regular expressions xD

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)?

1. Get an idea
2. Plan the structure to use overengineered solutions
3. $ git init
4. Setup the barebones
5. $ git commit -am "initial commit"
6. Forget the project for the next several months, until another idea pops out and you visit your github to setup a repo for the new project and rediscovers this miserable project's repo
7. Back to 1, repeat

The first project I used Source Control with.

At my university, we were told that it would be a lot easier, and that we were required to use SVN, and not Git. Me not knowing much about either, decided to learn from two people who used Git.
Confused as I was how it all worked at first, we spent a couple hours trying to work out a work flow, and how we wanted to use it.

Eventually, I was like "Guys, I got it!" And explained how we should do it. Then then said
"That's how Git works"

We decided to use Git, and at the last minute shoved everything onto the school's SVN server they had for the team.

Been using Git ever since. Looking back, not sure why it was so hard, but I am glad to have found Git instead.

I mean yeah I use command line Git to manage sets of Minecraft mods. It's not a big deal or anything.

Every time when I reach an achievement. For example my first XY or when I start to use a new tool eg. Git. But I get disappointed after I think about that I can't share my experience with anyone. Even my classmates can't understand me. 😕 Any tips?

That time when your company use subversion for a git repository...

I'm starting a freelance project and the guy who is working on the backend refuses to use git because all the files sync to his computer from the server

For our robotics team we have a college professor (if that's what you even call it) who is teaching our programming subteam how to code the robot in c++. Whenever we mention git he goes on and on about how git is too confusing and we shouldn't use it even if we used pull requests.

What the actual fuck

Am I the only developer in existence who's ever dealt with Git on Windows? What a colossal train wreck.

1. Authentication. Since there is no ssh key/git url support on Windows, you have to retype your git credentials Every Stinking Time you push. I thought Git Credential Manager was supposed to save your credentials? And this was impossible over SSH (see below). The previous developer had used an http git URL with his username and password baked in for authentication. I thought that was a horrific idea so I eventually figured out how to use a Bitbucket App password.

2. Permissions errors
In order to commit and push updates, I have to run Git for Windows as Administrator.

3. No SSH for easy git access
Here's where I confess that this is a Windows Server machine running as some form of production. Please don't slaughter me! I am not the server admin.
So, I convinced the server guy to find and install some sort of ssh service for Windows just for the off times we have to make a hot fix in production. (Don't ask, but more common than it should be.)
Sadly, this ssh access is totally useless as the git colors are all messed up, the line wrap length and window size are just weird (seems about 60 characters wide by 25 lines tall) and worse of all I can't commit/push in git via ssh because Permissions. Extremely aggravating.

4. Git on Windows hangs open and locks the index file
Finally, we manage to have Git for Windows hang quite frequently and lock the git index file, meaning that we can't do anything in git (commit, push, pull) without manually quitting these processes from task manager, then browsing to the directory and deleting the .git/index.lock file.

Putting this all together, here's the process for a pull on this production server:
Launch a VNC session to the server. Close multiple popups from different services. Ask Windows to please not "restart to install updates". Launch git for Windows. Run a git pull. If the commits to be pulled involve deleting files, the pull will fail with a permissions error. Realize you forgot to launch as Administrator. Depending on how many files were deleted in the last update, you may need to quit the application and force close the process rather than answer "n" for every "would you like to try again?" file. Relaunch Git as Administrator. Run Git pull. Finally everything works.

At this point, I'd be grateful for any tips, appreciate any sympathy, and understand any hatred. Windows Server is bad. Git on Windows is bad.

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.

I realised, that Git now has the same problem as Windows:
Its widespread because its widespread.

There are, especially for smaller projects, few reasons to actually use Git instead any other VCS.

Look at the landscape of free repo hosting.
There are hundreds, if not thousands of free Git hosters.
A handful of free Mercurial hosters,
Launchpad for Bazaar and I didn't even find a free SVN hoster.

Everyone uses Git, because there are Services for it, and there are Services for it, because everyone uses it.

The moment you realize your co workers don't really know how to use git....

Guys kill me please...
WE USE CLEARCASE AND ANT
Because git and maven are still under evaluation....
Am I working for the wrong company?

I actually love GitKraken, it's a very cool and awesome Git Client :-)
It helps me a lot and saves time.

Do you use it?

I cant wait for edgey hipster SoDev students to start talking to me about underground git repositories that they use. Although, at least they'll stop talking to me about ML, NN, and crypto.

Why use git, do it simple, send me your changes by email and I will merge it.
Why split split source code (js) into different files, use one so we will no have trouble about load order.
Use the same user account for github/gitlab/bitbucket/etc. So we will no worry to setup access permisions.
Use Dropbox/Drive for version control.
We will test the whole system until the end when all is finish.

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.

Never use random non-reversible git features on your 3-month project's master while just assuming and not actually knowing their functionality.
Or to avoid that altogether: Don't drink and git.

Hey guys!! Can anyone tell me from where I can learn how to use git..

Our team has finally moved to git fron svn and i'm loving it. I don't understand why would anyone use svn 😐. Would like to know if any of your team uses it

Confession: I know how to use Git but I want to learn how to use it properly so my team won't crucify me.

That I really hate svn.
It is completely useless compared to git and I can not understand why one would use it for any project with more than two people.

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)

It’s funny cause I don’t use GitHub much and don’t know git... yet. So basically I don’t understand all those git jokes. I only used GitHub a few times, and it was without the desktop app (which I find fucking stupid since you need to “clone” everything....

Getting a new laptop tomorrow, and was planing the process of setting it up.

Steps for new windows computer
1. Delete all included software... all of it.. call an exorcist if needed. Cast out the demons. Seriously, fuck you norton, and fuck you mcafee.

2.Use Edge to download ANY other browser.

3.edit system files to disable Edge, because fuck Edge.

4.install linux subsystem.

5.intall linux software like git, and use git to restore rc files.

6.party all night (code)

Spent like 5 hours today installing, configuring, and playing with phpstorm. first time I've used a real ide type program and wow, I replaced 5 programs with this I would use at the same time.

filezilla (ftp), rapidphp (code), mysql workbench, cmd prompt (node, gulp, sass), and source tree (git)

When your teams lead developer still uses unsecured FTP to deploy websites, does not use git or svn and would rather build their own cms than use an off the shelf product.. I can't help but learn bad practice's as a junior!

!rant

So this has probably been asked loads of times but I've never seen it. When working on solo projects for yourself do you still use source control like git or mercurial?

I usually don't because when I do personal projects its usually filthy and fast development to prototype quickly.

However, this current project I'm working on I am using git and I'm finding that slowing myself down just to follow good practice is actually improving my code quality and my understanding of my own project.

God damnit!!

Just got a team assigned for the course I follow and the codebase they work looks like someone shit on the floor and dragged it all over place. No consistency, no clear structure.

The project has to be built in PHP (which is fine by the way) following the principles of MVC. Did I say the codebase looks like shit all over the place? Well that's exactly what it is!!

They use $_SERVER['DOCUMENT_ROOT'] everywhere!! In every fucking file!! Why the FUCK would someone possibly want to do that??

I know I'm not perfect, but what the fuck!!

Now comes the most weird thing. They have to work on a remote server without SSH access, so working with FTP is mandatory. This is because the school won't setup ssh. That's fine by me, but because of that they don't use git!! They upload files directly to the production server. They merge everything manually. I asked why they didn't use git and the answer was so fucking SHIT!! "Because the teacher wants to see who uploaded to the server.."

First off all: what happened to git blame? Second: Later I heard that there is only one FTP account, so all the things they said where just bullshit!!

The fuck.

Tomorrow I'm going to try and convince them to use git..

How well do you speak git? Name all commands you know how to use 😄:

init, add, commit, remote, cherrypick, push, rm, rebase, reset, submodule.

Did I miss something?

Me: Ok I've updated the docs, I'll open a PR with the changes

Maintainer: Looks great! Can you remove the changes to the package-lock.json? (I assume it got updated when you ran npm install to start the webserver)

Me: Ok sure, I'll update it soon

And this is where the troubles begin. The file was commited 2 commits ago, so I have to roll back to then. However, the remote repository has been updated since then, so I git fetch to keep up to date.

This makes the rollback a hell of a lot harder, so I run git log to see the history. I try a reset, but I went back to the wrong commit, and now a shit ton of files are out of sync.

I frantically google 'reset a git reset', and come across the reflog command. Running that fucks things up even worse, and now so much shit is out of sync that even git seems confused.

I try to fix the mess I've created, and so I git pull from my forked repo to get myself back to where I was. Git starts screaming at me about out of sync files, so I try to find a way to overwrite local changes from the origin.

And by this point, the only way to describe what the local repo looks like is a dumpster fire clusterfuck that was involved in a train wreck

I resolved the mess by just deleting the local copy and git cloning again from my fork.

I gotta learn how to use Git better

You know what fuck github , anyone remember when git cli was easy and straight forward to use

Now i have conflicting master branches because the remote is main and git automatically defaults to master.

Git still asks for a password while github can't wait to inform me how I have to go through the very long process of setting up an auth_token.

Apparently https remote origins for some reason don't work anymore, why because apparently i need to change them into ssh, good luck with the public key errors

This sucks , fuck github and fuck politics

We crack jokes at each other and use profanity at all times. Troll other teams with funny git commits. Our slack channel is filled with weird giphys. Currently the most productive team according to the Chief Architect. How open is your work environment?

How much do you guys use CLI and why?

I did learn a bit of terminal as well as cmd as a hobby, but now I don't use cli that much anymore, maybe sometimes for git or fixing some issues... perhaps that's because:
1. I use windows
2. I am a .Net developer

What os to put on a slow 1.1 ghz dual core 4gb ram netbook?

Would like to use it for ad hoc coding, browsing, git and stuff again, but it performs horribly with Windows, Ubuntu, SuSe or elementary..

Preferably linux.

I usually start with a MindMap where I try to write down every bit of the idea.
I then try to set requirements and set the tools/frameworks I want to use.
Next step would be data model and then git started ;)

In SublimeText, I noticed that my markdowns formatting was not showing up correctly— I decided to download the new markdown package altogether hoping for some kind of update/fix. Turns out the package comes with a super ugly color theme which overrides the default theme of SublimeText. After some googling and experimenting, I found way to override this through the package settings. I always use git through my terminal but I thought let’s try to use git through my code editor and see how it works. I downloaded the git package but then I notice that git tool shows status and all correctly but doesn’t push files to GitHub (it says fatal: unable to read current working directory). Then I download another application called SublimeMerge. It works correctly on its own (pushes files to GitHub) but SublimeText is still not doing the same. Then I tinker around with my SSH keys hoping for a fix, but nothing works. I even go to stackoverflow and search for a solution but I find nothing (I even wrote a post asking for a solution but no replies till now). Fuck it! I now open the file with VSCode. Open terminal within VSCode and add/push/commit through it and everything works perfectly. So goodbye SublimeText I guess 👋🏾

Well, it happened, my school managed to block SSH

It also means no more git, and if this shit isn't fixed I might be forced to use TFS

Whoop de doo

First rant... I'm on a large project where en use Git. Apparently I am the only one who, after pulling the dev branch, do multiple local commits to track (and possibly) undo my local work before I merge into development again. Everyone else do ONE local commit. Am I gitting wrong?!

Im left speechless today when my boss (a dev for over 10 years) prefers to use WinMerge to manually merge frequent code changes instead of using the GIT source control.

- git => did you use sourcesafe anytime?
- VS Code => because everyone is against MS ;-)
- hammer (for keyboard) => self explaining

Windows 10 in dual boot.
It reminds me that I should care about the people who use my products.
Other than that, all usual things sublime, git, TERMINAL, Jetbrains

Why use git when you have dns TXT records?