So git tracks the history of your commits and gives you the ability to restore your project to any exact commit. For text files that is efficiently accomplished by only tracking the delta between text on each commit. For binaries, git can only compare file hashes and if the file changes the whole file is uploaded again in full to your history. You probably changed a few 1mb images a bunch of times and now have every copy of it in your git history. Git LFS solves this problem. You can pull the problematic files out with a tool that rewrites history, but rewriting history is usually not great idea, there are too many footguns.

  • source
  • [–] 7 points 10 months ago

    For the future, git is highly resilient so squashing the commits still leaves all the data in the reflog. After you do that operation a git gc would be needed to remove any unreferenced commits and shrink the git folder.

  • source
  • parent
  • context
  • [–] 4 points 10 months ago (4 children)

    Rewrite history. Use git rebase to squash all commits between adding and removing the blobs. Its gross, and if your project is publically used you need to tell everyone what your doing and why.

  • source
  • [–] 9 points 1 year ago (1 child)

    I was feeling super low this morning. And then one of my favorite fediverse heroes dropped this hotness on me, and I truly feel like I can keep going. This is wonderful, thank you for sharing Sunshine, I'm in!

  • source
  • [–] 10 points 1 year ago

    Filling out forms to get CI runners means no serious users will be attracted.

    I think this will have opposite effect. Only serious users will be willing to fill out forms and casual users will be put off by the bureaucracy. I agree that it is a downside though. In a perfect world, there would be no forms to fill in.

    The problem with CI is that the internet is full of not-nice people who will use free compute to mine crypto. Gitlab had problems with this abuse and requires credit card details.

  • source
  • parent
  • context
  • [–] 0 points 1 year ago (1 child)

    Be realistic. Filling out forms to get CI runners means no serious users will be attracted. They can just go to GitLab instead. And even then, a migration wouldn't be fully seamless.

    Those are immediate show-stoppers before we get to contributor pool sizes and network effects.

    My purist young self picked Gitorious over GitHub. I even vaguely remember the KDE presence there, so it was a trusted host with big(ish) betters on it. But it closed shop soon after, and that was a quick learned lesson.

    I will be more intrigued by the first jj-native forge when it appears. I may even help alpha test it, as it may bring a breath of fresh air to the space, unless it's going to be AI buzz-filled. In that case to the trash blocklist it will go.

  • source