• sgibson5150@slrpnk.net
    0·
    4 months ago

    Hey, sometimes you need to hose out the cruft.

    Why yes, I do maintain a legacy application that still stores user files in Program Files in blatent violation of 15 years of Windows best practices and continues to be done contrary to my repeated advice, why do you ask?

  • Wilzax@lemmy.world
    0·
    4 months ago

    Why learn how to use the entire swiss army knife when you can keep it closed to use it as a very small hammer?

    • JPDev@programming.devOP
      0·
      4 months ago

      git rm -rf is only usable within the scope of the git repository and removes files in the staging area and working directory but doesnt affect untracked files or .git. rm -rf affects everything. For this case rm -rf probably would be the better option

  • RustyNova@lemmy.world
    0·
    4 months ago

    Delete container, rebuild container. Sometimes it’s just useful to clean up all the mess of cache files

    • PotatoesFall@discuss.tchncs.de
      0·
      4 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.

    • Ephera@lemmy.ml
      0·
      4 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.

      • nous@programming.devEnglish
        0·
        4 months ago

        I have never had git get into a state I cannot get out of. Even if that is a reset, checkout or clean. And those are very rare. How are people breaking things so often.

        Learn the tools you use daily, it saves you a lot of headache in thelong term.

        • Ephera@lemmy.ml
          0·
          4 months ago

          Oh yeah, but I’m talking about the internal Git state just genuinely being broken, for example: https://stackoverflow.com/questions/14448326/git-commit-stopped-working-error-building-trees
          Ultimately, if you spend half an hour debugging that, it just starts being a waste of time compared to cloning anew.

          As for how to merge, yes, one should learn that. The problem is that the complexity of the code changes adds on top of whatever insecurities you might still have with Git.
          I did put “inexperienced” in braces there, because even as an experienced dev, merges are sometimes just not worth doing. In that case, you could just checkout the branch a second time, but well, still not that different.

      • RecluseRamble@lemmy.dbzer0.com
        0·
        4 months ago

        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.

        Pretty sure that’s actually it. Git has a learning curve and, for example, some naive rebase not working out as intended can be scary if you don’t know what you’re doing.

    • Johanno@feddit.org
      0·
      4 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
        0·
        4 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

    • SirQuackTheDuck@lemmy.world
      0·
      4 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.