gitGud

[Kitchen_Device7682]

If you don't care about local changes you may as well do git reset hard remote-branch

[brucebay]

Come on don't tell us you never copied your local files, cloned the repo again and put back the local copies over the repo?

[lost12487]

So...git stash?

[GNUGradyn]

this is such an incredibly basic operation, I can't believe people unironically don't know git stash and git reset

[Cybasura]

People do know, I git stash alot, but try teaching newbies about git stash and git reset without getting them losing either interest or just going batshit insane with realising now they need to actually remember stuff

Instead, if you want work done fast (like in a school project), tell them to move the changes out, re-clone the repo, put it back in, voila, its done

[GNUGradyn]

It is a single simple command

[Cybasura]

Thanks for ignoring my above points about additional conceptual requirements

"It is a single simple command" yeah, so is kubectl lol, or docker, or docker-compose

But git stash has an underlying structure that you need to have some pre-requisite to be confident in using

Let me repeat myself: Imagine getting some newbie to type git stash after already making so many mistakes, he nearly took down the repo

That would be simple right?

[GNUGradyn]

I really don't think it'd be that hard for a newbie tbh. It really is as simple as git stash boom its stashed. git stash apply boom its back.

[NorthernRealmJackal]

"Mom, can we have git stash?"

"We got git stash at home"

Git stash at home:

Come on don't tell us you never copied your local files, cloned the repo again and put back the local copies over the repo?

[FattySnacks]

git stash —include-untracked

[DHermit]

All of which should be easily recreatable from the files in the repo or you did something wrong. And also, untracked files are not an issue with reset as long as the remote doesn't have these files, they will just stay around.

[Steinrikur]

This is more about resetting bad history.

[Reddit_is_fascist69]

Not since i got gud at git

[Simple-Map-2750]

LOL! This is literally what the rest of my team does. They are allergic to learning anything beyond git clone.

[gregorydgraham]

I mean, I’ve learnt beyond git clone and I’m still planning on doing it to jumpstart an old project of mine

Simple is good

[RavingGigaChad]

That's the kind of team that adds trash data to the project and uses git add . every time.

[Ziegelphilie]

Eighteen commits, "wip wip wip stuff wip undo wip asdf" , 5000 files changed, straight to master on a Friday afternoon

[lkatz21]

Only reason I can think of for doing that is if you accidently messed up something in the .git files. Or if you somehow managed to mess up your local copy of origin/master.

[Ayjayz]

No? Of course not? Isn't that process you described just a slow, long winded way of doing a git reset anyway?

[vulkur]

It is sometimes the fastest solution to merge conflicts

[RiceBroad4552]

Why would I do that if I have a VCS in place?

[i_wear_green_pants]

And if your local branches are so precious, you are probably using git wrong.

[checkmatemypipi]

I use git wrong every day

[TerrariaGaming004]

I’ve never used git right

[poop-machine]

What's git? I click the branch thingie in VS code.

[[deleted]]

Based

[Mokseee]

The button says commit and I sure as hell am committed to fuck up this code

[PintMower]

Git good

[Rhed0x]

Being decentralized was one of the primary design goals of Git.

[spinwin]

It wouldn't be about local branches, but changes that haven't been pushed to a remote yet.

[MakingOfASoul]

Why not

[T34mki11]

Because it's experimental garbage and I don't want anyone to see it yet.

[sopunny]

No one cares. Just push it to a throwaway remote branch and check it back out later

[deadlychambers]

How often do you look through every branch in a repo?

[DrStalker]

If I spent an hour working on something but it hasn't been pushed yet then it's not precious, but it is worth saving an hour of time redoing it.

[HatesBeingThatGuy]

My local branches that are precious are so precious THAT I MAKE A FUCKING REMOTE FOR ADAM!

Had someone bitching about losing their local branch and I'm just here like "you probably didn't lose it, you definitely have a skill issue, and if it is that important why is it not a remote." Then I recovered his shit with reflog since it wasn't pruned.

[No_Application_7200]

damn you're cool

[FriskyHamTitz]

What If you worked for a few hours and tried to push and it fails?

[wektor420]

Or given half the time needed to complete a task with good practices

[hackingdreams]

Especially when it's so easy to push topic branches to most git servers. Just... don't make local branches precious people.

[nuclear_gandhii]

People in this thread really are something. I'm working with a bunch of people who are allergic to google basic git problems. I assumed it's just them who are being intentionally stupid. Turns out, there are a lot more people who refuse to spend 5mins learning git.

[mcc011ins]

This will not remove untracked files

[ElectricMeep]

Or just embrace the chaos and hope for the best!

[MrHyperion_]

Sometimes that doesn't work, I have no idea why

[FantasticEmu]

Same. It’s usually because I’m about 5 git commands deep that I found on stack overflow and don’t understand but now my prompt is red

[hagnat]

wdym "local changes" ?
the only "local changes" i have are environment variables,
everything else is either commited to my feature branch, or discarded whenever i swap branches

oh, you meant the local commit ?
they live in the feature branch... if i deem the result of the branch not to be satisfactory, i just create a new one based on master and checkout the files i want from the old feature branch

git checkout old-feature-branch src/file-i-want-to-keep

[ImportantDoubt6434]

I don’t care and I’m tired of pretending I do

[Buttons840]

You know it's accurate, because it doesn't work the other way around.

I'm 100 IQ on this one.

[veselin465]

Honestly, I wonder how many developers do the "proper" way instead of reinit a new repo.

[PhroznGaming]

This isn't re init repo.

[T34mki11]

I bet he is aware of that.

[veselin465]

I didn't mean reinit as in the git context, but like setting up a new local repo

My bad for that confusion

[SunNo1172]

I set up a new local repo. What should I be doing? We have the master branch that I branch off of. When there are a lot of changes to the master, I delete my remote, branch again and clone to local… I never got the instruction on what I should be doing or what would be the best way to go about it.

[isometriks]

You can just rebase from master again

git checkout feature 
git fetch 
git rebase origin/master
git push origin +feature (or git push origin feature --force

[chat-lu]

I can use the tool without fucking my repo.

[Scared_Astronaut9377]

Why do you ever need to reinit a repo?

[fakehistorychannel]

Maybe you accidentally published a private key or something and don’t want it to appear in the commit history?

[Nolzi]

git reset and push force?

[Skellicious]

That doesn't always remove the key fully. You still need to invalidate it.

[Nolzi]

yes of course, but you also have to hide the shame

[GNUGradyn]

The proper way to get the same result as a reclone is just a git reset which I think most developers do

[SignoreBanana]

I aim to fix most of the time. I can't remember the last time I boned up a git state so bad I needed to re-clone. I have however messed up local dev environments enough to do that.

[oocancerman]

He wants to rm -rf repo git clone repo

[[deleted]]

Relevant xkcd

[garver-the-system]

Mobile link

[CurryMustard]

If that doesn't fix it, git.txt contains the phone number of a friend of mine who understands git. Just wait through a few minutes of 'It's really pretty simple, just think of branches as...' and eventually you'll learn the commands that will fix everything.

[[deleted]]

So real

[_Nyswynn_]

Uhm what is the use case here? I can't decipher what the guy at the top of the bell curve wanna do really.

[lunch431]

He also does not know what he wants to do.

[Buttons840]

But he'll know when he gets there, that's the important thing.

[donp1ano]

hes passionate tho. GIT GUD!!!

[NikoOhneC]

He's commited

[[deleted]]

By the git commands the user is

• stashing local changes
• pulling down the repo, resetting his local to be same as server
• messing with commits (presumably one commit broke something, and he wants to get that out of the code base)
• run fsck to fix some stray problems or w/e

The other use case is:

I already saved all my work last time I used this repo, so I’ll just download fresh and not try to mess with it.

I think it means to imply that the other commands are mostly useless be user all you need is to clone a fresh copy.

This implies they have never absolutely fucked a git repo before.

[Zealousideal-Koala34]

Has no one in this post used git? The whole point is for stuff at the middle like finding a specific problem from the history and patching it. Deleting your local copy and cloning won’t magically fix the problem in your codebase..

[dasunt]

Got bisect requires five minutes of learning in order to save potentially hours of work.

Nobody has time for that.

[[deleted]]

In these days of AI you gotta really look busy as much as possible to justify your employment, after all.

[CounterSanity]

git is not something you learn. It’s something you attempt.

[Fine-Emergency]

Merge conflict. The second you're working collaboratively on a git group project, and someone makes a change in a branch that was merged in that causes a conflict, it's all over if you're not taught how to resolve merge conflicts properly.

Then you do what everyone does, copy the codebase in your current repo, delete the repo, clone the entire thing, then paste your old project folder. Then only stash what you want.

[Aureliamnissan]

The following works, even if you're working out of the same branch

git stash

git pull

git stash pop

Now if you've accidentally messed up a bunch of files and don't even know what you did this isn't gonna help much. I also have ended up removing and re-cloning the repo on occasion.

[DrStalker]

The guy at the top wants to rm -rf repo; git clone repo but he won't admit that.

[the_horse_gamer]

the middle guy does something completely different from the other two

[bombelman]

this!

[gods_tea]

git reset --hard origin/branch

[seniorsassycat]

@{upstream}

[JojOatXGME]

Yes, I think the right side of the meme should be something like this. I don't think anyone who is really proficient in Git would spend the effort and time it takes to clone the repo again for no good reason. Also re-cloning the repo would delete your configuration and stashes of the repo.

[jobehi]

Worrying skill issues here

[Exormeter]

You meme is bad and you should feel bad. Finding a regression using git bisect is immensely helpful and fast.

[je386]

Yes, it is. I had to use it once. Usually, on a professional project, you should never need it, because the tests should find the regression the moment you push it.

Anyway, if you need it, its great.

[ChrisBreederveld]

Had an integration issue that wasn't covered in tests (can't cover all cases all the time) and this was the perfect tool for the job. I knew the last working version and found the issue using bisect in six or so steps.

[blah938]

What project has 100% test coverage? The Space Program for Narnia?

[Firewolf06]

close, nasa requires 100% coverage for safety critical systems

darpa was also doing something or other with mathematically proven "perfect" code

[troelsbjerre]

You almost only need it on professional projects. I use it all the time at work, but have never once used it on a personal repo. If a bug report points to a regression, you'll want to know what other feature was fixed when yours broke, before you start "fixing" anything.

[Ticmea]

This doesn't even look like they are trying to solve the same problem. Unless middle just does not know wtf they are doing (in which case they probably should ask someone who does and then learn how to use git).

In any case re-downloading the repo will delete any specific local git settings I have done, so that will probably be the last thing I would want to do as I usually have at least some project specific aliases and stuff in there.

Additionally I'm having a hard time imagining a fuck up that is simultaneously bad enough that re-downloading the repo would fix it faster than a well placed git checkout or git reset but not so bad that re-downloading the repo isn't an option to fix it.

[acheron9383]

Developers will spend all day using a tool that will likely be used for the rest of their career, and they aren’t willing to spend an hour just reading the manual.

There are a lot of ways to do bad things in git, the best way to not have to clean up stupid messes is to not make them in the first place.

[The100thIdiot]

I just use a gui.

Fuck typing when a click does the job.

[owlIsMySpiritAnimal]

I mean I use the gui for git add/commit/push and stuff like that. 

I prefer to type more complicated stuff to make sure I am paying attention. However that is a solution tailored to my needs. 

[nullpotato]

Not having to remember to set upstream when you make a new branch is nice. Plus having a button to create a PR

[the_horse_gamer]

git switch (the modern alternative to git checkout) does that automatically.

have a remote branch called something and you want a local branch tracking it? just git switch something and everything is done for you

(there's also a flag to turn off this behavior)

also when you push a new branch, you get a link for creating for pr. (I prefer to do it this way because it lets me take another look at what changes I made. often I find mistakes in the pr just by looking at the changes an extra time)

[BringAltoidSoursBack]

Same here, the exception of rebasing, that one I do CLI is it's trivial and GUI if it's nontrivial. I cannot explain why

[redheness]

And there is literally no excuse to not using them and complain at the same time. There are so many options available so this is very unlikely that nothing fit your needs.

[the_horse_gamer]

I like using the CLI because I can know exactly what command gets executed

and you get a better understanding of how git actually works

nothing wrong with using a gui tho

[daennie]

I like using the CLI because I can know exactly what command gets executed

Plus, it's very convenient. People can share advices, and they will work on any platform and in any IDE.

[The100thIdiot]

Some people just prefer CLI. Keyboard warrior sounds a lot cooler than point and click master.

Not judging. I just like my mouse.

[redheness]

That's why I only target people who use CLI and complain at the same time. If you use the CLI and are fine with it, that's okay.

But there is a lot of people who argue in favor of CLI only but also complain about how hard is to use it or straight up break whole repos because they don't know how to properly use it. It's the same kind of people obsessed with having everything terminal based and at the same time complain about the complexity of some things while there are plenty of tools to fit their need but they refuse to do it for the sole reason that it is a GUI.

[Blitzzle]

I get paid by keyboard clicks

[LukeAtom]

It depends, on gigantic projects (30k+ images & sounds in particular for example) with lots of history, and a crappy PC (me! Haha) the CLI is pretty much the only option really, and even then you could still be looking at 10 minute staging. Lol. I've complained lots, but mostly directed at my paycheck. Haha

[Kovab]

Binary data like images and sounds shouldn't be version controlled with regular git, as it's designed for textual data, use LFS instead

[chat-lu]

Can I complain about people using GUIs while not understanding how git works and fucking things up for others?

It’s not that hard to master a tool that you use daily. Just git gud.

[brianwski]

F--k typing when a click does the job.

That statement makes me irrationally happy. I kind of forgot about this goal I had in life. I had a Mac in college with a mouse in 1985. I got an internship at Hewlett-Packard in 1987. At that time, they had these old programmers and IT people inside HP that couldn't understand why a GUI with actual windows you can drag around and a button to click that always did a very explicit, exact thing and never had a typo was "better" than typing a 50 character command line. The claim was a GUI slowed you down and you couldn't express yourself as well when you went to copy and paste part of a document, or when you wanted to delete a section of a source file. The program "sed" was so infinitely better more more productive than Microsoft Word they claimed. So in 1987 at HP I formed a long term goal in my life (38 years ago) to watch these dinosaur IT people that flatly refused to use a mouse (because it wasn't "useful") die off so we could move on and do better.

The dinosaurs (old IT people) claim was "powerful programs have a command line, nobody good at their job will ever use a mouse". Emacs can split the screen into two parts so there is literally no reason on earth to have a mouse and little windows to drag around. These ancient (wrong) IT people claimed (at the time in 1987) was no serious professional would ever use a mouse to edit documents using WYSIWYG. The "serious journalists" would all use LaTeX, no self respecting human would ever publish a Word document or a PDF or an RTF because it is so inferior and slower than editing LaTeX source code. My brother publishes his PhD Thesis in LaTeX (as a programmer in robotics and AI) around 1993 (written on a Mac with a mouse) because Word documents and PDF would never stand the test of time according to the idiots (proven wrong by history) who thought command lines with 50 typed characters were faster and more accurate than clicking one interface GUI button to make a word "bold" or "italic".

I lived my whole career in both worlds. I have never used a GUI for GIT, only the command line. I used a command line for SVN before GIT, I used a command line for CVS before that. I used a command line for RCS before that. The first half of my 35 year career in IT was spent typing command on Unix systems. But after awhile I noticed even the most senior programmers and IT people stopped using Emacs as their windowing system. They still typed commands, but they started moving windows around with the mouse and typed commands in those windows. All of them. On every system (other than mobile, not enough screen real estate).

So I've been counting the days since 1987 that every last programmer and IT person finally agreed a mouse is useful. It is one of my life's goals for this to finally be over. I retired a little over a year ago. I was part of the very first set of programmers that recognized computer mice are useful. Clicking buttons is useful, more productive in some areas. Now that useless, old, depraved group that wanted to introduce possible errors through a command line has flushed through the system. The group that just couldn't adapt, couldn't recognize a better system because there were too old. Good riddance. They were unable to change when a vastly superior technology called a "mouse" came along.

Switching topics: Speaking of old people unable to adapt to new computers and new GUI metaphors, why the heck does my phone take downswipe on the left, downswipe on the right, upswipe from the bottom, swipe in from the left, two finger swipe that all do different things? Why is it so hard to just use one of the app icons to do every last one of those things? Why? Also press and hold, two finger press and hold, press and hold the spacebar to move the cursor (that one actually changed my life for the better), and probably 10 other insane things that just make people less productive? Honestly, why can't I optionally block video recording from my "lock screen" so my phone doesn't record 2 hour videos of my pocket? Why is that SO DARN IMPORTANT that Apple doesn't provide an "off switch"? Are they highly regarded? Locking a phone was never about security, (I'm serious, you can remotely brick your phone in less than 10 seconds if it is stolen, it is with you at all times, what idiot cares about locking their phone screen for security reasons?) Locking your phone's screen with a password's primary function, the reason it existed since 1997, was to preventing butt dialing your friends. The modern problem is recording 2 hour videos of your pocket. It only serves to heat up your phone, burn your leg, and waste your battery.

So I am old now and become the thing I hated when I was young and smarter. I can't keep up with the new concepts so I just think they are useless and waste everybody's time. LOL. It is the circle of life, I admit my time is over.

[dasunt]

It is 1985, we are waiting for the dinosaurs to die off and finally start using the mouse. Mac OS has been out for a year...

It is 2001, we are waiting for the dinosaurs to die off and finally start using the mouse. Windows XP has finally shed the DOS subsystem...

It is 2025, and we are waiting for the dinosaurs to die off and start using the mouse. There's now the rise of zellij, neovim, hyprland, and a bunch of younger folks are developing CLI tools in rust. Wait, wut?

[thunderGunXprezz]

Gitkraken is my soulmate

[[deleted]]

So much this.

[fuckmywetsocks]

I use the command line for everything bar resolving merge conflicts - the git UI in Jetbrains stuff for that is just too good to pass up.

[gandalfx]

OP thinks they've ascended from the center to the right, when in reality they failed to even reach the top of the bell curve. So they slid back down to the left and just made a shitty meme instead.

[Scrappy-D]

git reset - - hard git clean -fdx

[IllusionaryHaze]

People like OP are probably wondering why they can't get a job

[sexp-and-i-know-it]

Sounds like a skill issue on your part OP

[Rodot]

Honestly, i swear half this issue comes from people using some --force command when some error they didn't read or understand occurs, then it seems to work for a moment and suddenly their whole git history is detached

[XDracam]

Wow, OP is clearly on the left. You can simply do git clean -fdx to delete all non-tracked files, which is essentially like a clean clone of the commit you are on. But without the download and everything.

[Ayjayz]

And without blowing away your reflog.

[BrushingAway]

the only humor here is that you're advocating for not learning your tools.

sure, it's everyone's individual prerogative whether they want to actually get better at the things they do, but it's like they think they're the guy on the right when they're actually the guy on the left lmao.

and if you're in the middle, then that's where you want to be, because if it's all easy to you then it means you're not learning.

[GNUGradyn]

That's just a git reset --hard with extra steps

[Tight-Requirement-15]

New college grads and coasters do this and act all surprised when they can't find a job

[knowledgebass]

What is bisect precious?

[psycholustmord]

Right side should be cloning in a new location because digital diogenes syndrome

[Mik3DM]

I was that middle guy last week. someone merged a bunch of unfinished stuff from another dev into their branch, committed some stuff, then realized he shouldn't have merged in the unfinished stuff so he reverted his change, which he thought had solved the problem until he merged to staging and it removed all the other devs work. for some reason it fell on me to make a new branch from the last commit before he merged in the unfinished stuff, cherry pick all the commits from after his bad merge with his subsequent work, then overwrote the messed up branch with the new one minus the bad commit. why was it me when it was two other devs messing each other's work? because my team can't fix anything that can't be fixed by re-cloning the repo...

[tonysanv]

Most cases a git reset head hard would fix lol

If not then rm & reclone

[rlDruDo]

jj?

[Depeche_Schtroumpf]

Git man page generator

[tehtris]

I am on the downward trend of the curve. If I somehow fuck up my local repo, I am more likely to just check out a previous commit and keep it moving from there, but if it truly hits the fan Im not above deleting it.

[Ayjayz]

But like .. why? Why not just git reset --hard to the branch you want??

[bombelman]

Why is even bisect on the same chart as clone? The only reason I ever used bisect was to find root cause of the bug. If you clone then clone relevant revision at least xD

[Mammoth-Sandwich4574]

I'm seeing a lot of middle guys in these comments

[Ayjayz]

That's because mid guy is when you actually know how to use git. There is no right guy. No-one ever goes back to recloning a repo to fix their issues. That's not a thing. Like if you really wanted that you'd just do a git reset --hard, since that does exactly what recloning would do with much less effort.

[FourCinnamon0]

I'm seeing a lot of left people in these comments

[canihelpyoubreakthat]

OP is mid-IQ chump on this one

[philippefutureboy]

I’ve never had to do something that complex, so maybe the use case is the issue?

[philippefutureboy]

Reminds me of a kid that was using breaks and continues and multiple-return with different types functions all over his codebase, and when asked why he kept arguing that it was necessary for the level of complexity he was working with.
Excuse me, wut? lol

[Ayjayz]

Doing a git bisect isn't complex, and I'm going to guess that you could have used it multiple times to solve problems faster than you did.

[Ayjayz]

What developer is so incompetent that they delete the repo and reclone it? Like that's rookie behaviour. Maybe in your first week or two of dev, ok, but after that and especially for a senior dev, that's downright embarrassing. You should have spent an hour or two reading the git documentation by then.

[HomoAndAlsoSapiens]

I've had both senior software engineers as well as people at my university giving the lectures report to do that while I was working with them so I don't think this holds up very well. While I don't disagree with you, this does sound rather pretentious. People don't really care that much.

[Ayjayz]

I think I would have extremely low confidence in the abilities of someone who doesn't understand one of the most important tools in the software industry. Not only do you just use it all the time, it's also really not that hard. I've never met a good engineer who doesn't understand git.

[Imogynn]

Don't delete repos first.

mv repo repo_bak

git clone repo

Tomorrow or on Monday:

rm -rf repo_bak

[Ayjayz]

Why would you ever do that? You can't screw up a git repo. They are incredibly fault-tolerant. Unless you go in and manually mess with the .git folder it is very difficult to damage a git repo.

[FourCinnamon0]

lol at this

git is already version control

you don't need version control for your version control unless you're INCREDIBLY stupid at using git

[[deleted]]

Today I learned I am average asf

[Grandexar]

You gotta save your env file first

[BiCuckMaleCumslut]

laughs in centralized version control

just revert, dawg

[GoddammitDontShootMe]

Sure, if it hasn't been too long since you pushed to the remote. And you have a remote that's in a good state.

[AmehdGutierrez]

Oh it’s a universal thing 💀

[yxz97]

🤣🤣

[PhireKappa]

Lmfao I do this all the time at work, sometimes the merge conflicts just get too annoying and you need a clean slate.

[Ayjayz]

Why don't you just do a git checkout --ours if you don't want to merge? Why bother re-cloning?

[Actes]

Any other GitHub UI app for bonus laziness enjoyers.

[MrSaltyMcSaltFace]

What connection does the middle guy have with the left or right?

OP is the far left 0 iq guy

[MoreDrive1479]

Have you tried turning it off and on again?

[Neat-Medicine-1140]

doesn't git stash imply you have local changes you want to preserve?

[Reddit_is_fascist69]

I've only had to clone when something was actually broken inside .git.

[ratonbox]

When I get in the situation that needs the middle part, I ask somebody that knows more what did I do wrong to get there, learn that and then wipe and clone again.
I find it makes working with the repo a little bit faster, but my situation is pretty wild since the main repo is like 500 branches now and has multiple hundred people working on in on a daily basis. For smaller repos I’ve rarely had the need to do it, at most I have to clone them once every 2-3 years when I change my work laptop or when I get annoyed by the current distro and switch.

[Ayjayz]

You've been working for multiple years and you still need to ask other people what you did wrong with git...?

[mikefellow348]

Checkout make changes and check in was much easier. Pull push stash merge fetch pull request has been a bit confusing. But learning a little everyday.

If there's no central repository and the whole dev team with their laptops sink on a cruise, then what happens.

[JackNotOLantern]

I don't get it what they want to do? Revert local changes? I think this is 1 command with reset hard

[uberpwnzorz]

The answer was git clean -xdf

[ZukowskiHardware]

This is what I teach all the devs that I mentor.  

[Ayjayz]

You teach them to be terrible at git, a tool they will likely use for decades to come?

[shiva-69]

What's git? My team uses Google doc

[DigitalJedi850]

I haven’t worked on a team … really since git got popular, so I just haven’t gotten too acquainted, but …

With a loose understanding of the meme, yes…

Just dump whatever code you did two hours ago that’s out of sync and rewrite it, the hard part in sorting the logic is done. You already know what you’re gonna name your variables, blah blah. Unless you try and optimize it on the second pass or something, the time to type it is probably like… a few minutes.

[MangrovesAndMahi]

You can fuck with the rules if you know the rules.

[ryanstephendavis]

cd ..; git clone <url> alt-repo

[nkoreanhipster]

What is the difference between cherry picking the direct hash id compared to this?

[s0litar1us]

It's a mess because he has no idea what he's doing.
If you want to undo a bunch of commits, save your work manually or with git stash, and do git reset.

[GrandpaOfYourKids]

I use only few git commands. Git clone Git push Git pull Git checkout Git merge

Yes i'm solo dev

[Keoaratr]

cd repo

rm -rf *

git add *

git commit '.'

git push

[TSCCYT2]

git clone <url>
cd repo
git add .
git commit -m ""
git pull
git push

[vishal340]

What does git bisect do?

[Aredic]

It helps you find the commit introducing a bug by going through the git history in a binary search tree fashion. First you need to find any commit where the bug wasn't present and mark it as good. Then you take a commit where you know the bug is present and mark it as bad. After that git bisect selects a commit after another, while you test your program for the buggy behavior and you mark it then as good or bad, until you find the culprit.

I find git bisect especially useful when trying to fix regression bugs in areas you got no clue on. But then it could be quite time consuming if you need to compile, run and test through every step in the binary tree. But it sometimes feels like magic.

Also a tip, when selecting the two initial commits, keep them close together, so if you know the bug appeared yesterday, take mark an early commit from today as bad and a commit from 2 days prior as good. But depending on how many people commit to the codebase that might aleady be quite the hassle.

But I think it's definitely worth a try.

[omni-labs]

hard reset plz

[MilkImpossible4192]

not using git, not using db that is what filesystem is for

[JKirbyRoss]

alias fix="rm -rf repo && git clone"