• PotatoesFall@discuss.tchncs.de
      link
      fedilink
      arrow-up
      9
      ·
      2 months ago

      People inexperienced with git can get stuck after doing some funky checkout / rebase stuff. If you don’t know your way around git so well, I guess this is the obvious solution.

    • SirQuackTheDuck@lemmy.world
      link
      fedilink
      arrow-up
      5
      ·
      2 months ago

      I’ve been doing this yesterday. Not because Git broke, but since Intellij kept pulling invalid configs from the cache, and that was based on some kind of path identifier it seemed.

    • Johanno@feddit.org
      link
      fedilink
      arrow-up
      3
      ·
      2 months ago

      Gradle!

      Fucking gradle. I do config stuff, rerun gradle error here, I fix the error rerun gradle: sth. Violation error.

      Ok intellij invalidate chaches and restart… Still same error.

      Fine I’ll do it again

      git add. 
      git commit -m "stuff"
      git push
      
      rm -rf repo
      git clone repo
      
      • iammike@programming.dev
        link
        fedilink
        arrow-up
        4
        ·
        2 months ago

        You can probably use something like

        git clean -xdf
        

        To get rid of all the artifacts not tracked by git, in this case it’s virtually the same as deleting the repo and re-cloning it.

        NOTE: Make sure everyhing is staged, otherwise that data is gone

    • Ephera@lemmy.ml
      link
      fedilink
      arrow-up
      1
      ·
      2 months ago

      It does sometimes happen that something in there just breaks and isn’t easy to recover. But it can also be a matter of (inexperienced) devs just deciding, fuck it, I won’t try to merge it, I’ll just copy my changes elsewhere and throw away the repo.