They slowly started locking down the platform for people without accounts and it has been really annoying to use the website since. First it was not possible to search for code, then even searching for issues got more and more difficult with it randomly failing, and now it's gotten to the point where I can't search for a fucking project anymore!
Github's search is becoming as bad as reddit's, where if you want to find anything, a secondary service like SourceGraph, GrepApp, or even a dumb search engine is better. Sometimes those haven't indexed what I need (especially code search), so I have to download the bloody tarball and rg for whatever the fuck it is I was looking for.
Sometimes it will also block the VPN I'm using, so I have to proxy to a non-VPNed machine. The world could do without these unnecessary roadblocks.
What also grinds my gears is requiring an account to contribute. There is no way to send in a patch, raise an issue, or anything without an account there, so by if a project being on github, you have no choice but to give Microsoft your data to participate in opensource. Don't get me wrong, mailing-lists are filth, but and I'd rather claw my eyes out than participate in any project demanding their use, but Microsoft being the "lesser evil" is not a good look.
Please, for the love of opensource, get your project off of github, please. It's a monopoly at this point and doing microsoft things. This isn't the end and they'll probably do more stuff to see how far they can push it. We'll all be the boiled frogs.
Yes, I know they have a CI and some other features, but if all you're doing is hosting your code, please consider an alternative.
Possible alternatives in alphabetic order:
- Codeberg (could have federation in the future)
- Gitlab (has CI)
- ~~OneDev (no git SSH clone but feature-rich)~~ not an instance for the public
- Radicle (no CI, but federated)
- Sourcehut (minimalist, but fast as fuck)
or maybe others will suggest more.
I'm sure you can just
--amendit and push with--force-with-lease(safer than just--force). That'll prevent the 78343 commits.Oh yeah, you can, but it makes it pretty much impossible to discern between commits in the action run overview. So, if something broke between one change and the other, then you'd have to just kind of know what that change was.
That is obviously doable, if you make a singular change, then wait for the result before you make the next change. But I often had the problem that I would get interrupted or that I had to continue on the next day, so when I wasn't quite as clear anymore what lines I changed precisely. Or what also often happened, is that I would get bored while I'm waiting for the action run to complete, so I start making the next change before I know whether the previous change was successful (I guess, this only really starts to become a problem, if it takes 30+ minutes for the run to complete).
But yeah, I put them onto a separate branch, so I can easily squash them into one commit before putting them back onto the proper branch.