this post was submitted on 24 Jan 2024
1 points (100.0% liked)
Open Source
31262 readers
189 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Damnit of course it was. Thanks for letting me know, now I'll have to redo my 100+ repos.
Changing the remote should be fairly trivial with enough bash skills
It's more I don't have them all checked out, and a good chunk are mirrors of github, so I'll have to list out each one and push to a new remote, mirrors will have to be setup again, and I also use the container and package registries. I'm pretty embedded. It's not impossible, but it's a weekend project for sure.
If it was just forked, cant you just switch the package/container-image and be done?
Depends on how much it was changed I'm guessing. Fingers crossed I could just flip it over, but who knows
Simply changing the binary worked for me. Been more than 1 month and no migration issues.
It does still show gitea branding, however.