[0]: https://codeberg.org/forgejo-contrib/federation/src/branch/m...
Then again maybe for stuff like actions and in general CI/CD it's not all that bad, you don't need whole team to know exactly how to write it, you just need to have a person knowing it. and it's generally not all that hard to learn.
There were some times were Codeberg's general performance was noticeably worse, but most recently it has been fine.
If you thinking of migrating a project with hundreds of issues, I would do a test migration and practice a few different searches to test the result quality.
Both forks originated for "philosophical" reasons, not technical ones and Joe Chen (@unknwon on GH) deserves a lot of the merit for building a clean forge in Go mostly by himself.
But I'm sort of disappointed the end result doesn't seem like it's any better for users? (not blaming the author)
The benefits for the maintainer are also mostly philosophical... Which is a shame
I just tried Codeberg
- I get constant "Making sure you're not a bot!" anime girls
- The login with Github is hidden behind a minuscule drop down arrow. Seemingly intentionally obscured.. either have the option clearly, or don't have it at all..
- the format is identical to github with zero improvements to layout. It still has the README at the bottom, where you have to scroll past a billion files to even see what the project is about. Ex: https://codeberg.org/dnkl/foot Why not just make the README the landing page, and then the file tree a separate tab? Or some horizontal side-by-side layout
Blindly copying the market leader and offering nothing new .. just doesn't seem like a winning strategy? It either indicates a lack of imagination or initiative. This space has some very clear room for improvements..
[1] https://codeberg.org/Codeberg/Community/issues/1786
[2] https://news.ycombinator.com/item?id=31627061
[3] https://blog.codeberg.org/we-stay-strong-against-hate-and-ha...
> Unlike other giant platforms, we do not encourage you to write “heavy” pipelines and charge you for the cost later. We expect you to carefully consider the costs and benefits from your pipelines and reduce CI/CD usage to a minimum amount necessary to guarantee consistent quality for your projects.
So much pretentiousness
It does break and go down; and GHA are a real pain in the ass. But the basic hosting and PR workflow are fine.
It's still getting things done, for sure, but no longer pleasant to work with.
That's the real problem with Github these days. Too much critical information behind throbbers that take their sweet time. I find Codeberg much more responsive, despite being an ocean away and having the occasional anti-AI-scraper screen.
I help with one of the most popular projects on Codeberg, Fuzzel. I can say we get no shortage of issues and feature requests from being on an alternative forge. Indeed, we have plenty!
I think I was looking for something like Migadu[1] for git hosting. Cheap, private and for personal use. The best option is probably to self host.
I tried to fish out some ideas with an ASK HN thread but it did not get any attention: https://news.ycombinator.com/item?id=46011054
I have started putting my new stuff in Codeberg. Some of the private projects have manually update private mirrors on GCP (free so far).
Gittea for self hosting is something I always wanted to try.
Bitbucket is slow to push to and pull from. From a reliability standpoint I have far more issues with Bitbucket than Github. The web UI feels completely off in a way that's hard to describe if you've never used it - it's like it was created as an afterthought or a skin on an older system, without any sort of craftsmanship behind it. There's also no source code search.
There's probably more, but quite honestly I try and stay out of the web interface of my bitbucket repos as much as humanly possible, so I shall stay happily ignorant of the rest. It's a shame, because I remember Bitbucket when it was the Github for Mercurial with a decent (if derivative) interface, and they allowed you to have private repositories without paying money.
Now, Bitbucket no longer supports Mercurial and Github gives you private repositories. Given those realities, why anybody would ever choose Bitbucket in TYOOL 2025 is beyond my ken.
This was incorrect, I misread the changes to the TOS.
Private repositories are only allowed for things required for FLOSS projects, like storing secrets, team-internal discussions or hiding projects from the public until they're ready for usage and/or contribution.
They are also allowed for really small & personal stuff like your journal, config files, ideas or notes, but explicitly not as a personal cloud or media storage.
So the ToS says only private repos that support FLOSS, but then backdoors into "small & personal stuff" which is pretty loose and up to Codeberg's discretion so probably not the best place for your private side project repos.Is there any recent event or broader trend that explains this shift?
The two ends of the spectrum, both source available and copyleft licensed code shouldn't be used for training, but who's listening.
citation needed. first they need to know my code exists... spend time and traffic crawling it because it's sure as hell not going to be hosted on azure... probably get detected and banned.
If you believe in absolute cybersecurity for anything you keep online boy I've got news for you. Literally all you can do is make it tougher but it will never be uncrackable. The degree of it depends on how much you can invest and suffer.
same here. codeberg makes in tougher so it's a measure.
[0] https://ziglang.org/news/migrating-from-github-to-codeberg/
I don't really have a choice but to use Windows and Visual Studio 2022 for work, but I've dusted off my Sublime Text license and have been eyeing migrating my personal repositories to Codeberg.
Everything else not important to them.
(I'm just keeping the metaphor alive because for me it is the primary blocker, whatever we call it.)
> Running CI/CD pipelines can use significant amounts of energy. As much as it is tempting to have green checkmarks everywhere, running the jobs costs real money and has environmental costs.
Honestly I think the mention of environmental costs has likely made users hesitant to sign up. Mentioning it costs real money is reasonable. Mentioning the environmental costs is not; the environmental harm is equivalent to the population buying a few dozen extra cars, which can easily be influenced by random marketing decisions by automakers and dealers.
In my experience reprimanding tech savvy people for the environmental costs of compute just doesn’t work. It’s far better to rephrase things into performance optimization problems, which naturally pique engineers’ interest.
typedload was the most difficult because I test it on multiple versions of python, but woodpeckerCI does its job so I can still run the tests even after the migration.
For the other projects I have I didn't bother to set up a CI since it's trivial to run locally.