Gitea has just joined the Fediverse on their very own instance, you can follow them here:

➡️ @gitea

Gitea is a free open source git platform, a self-hostable privacy-friendly alternative to Github. You can find out more on their website at:

There's a good video about Gitea by @hexdsl at:


p.s. If you like Gitea but you don't want to self-host, there's a very popular Gitea instance called Codeberg.

They are on the Fedi at @codeberg and their instance is at

You know your presence on fedi has been eagerly awaited when as soon as you join someone else writes your introduction before you do. =)

@FediFollows @gitea @hexdsl Isn't it kinda ironic that the project's code is hosted on GitHub? They should make their own instance and use that for development.

@MarcellusDrum Seems like a non-brainer, doesn't it?… has been "almost ready" for two years and other parts of the project have already migrated, but is still blank. Not sure what's going on.

@hexdsl @FediFollows @gitea

@clacke @hexdsl @FediFollows @MarcellusDrum

We have setup and ready for exactly that purpose, however we don't want to lose any information when migrating and so we have been testing migrations regularly. We run into many issues due to github's ratelimiting and they have refused to increase our limit. With 17k+ issues and PRs, with many comments in reach, plus release attachments and so much more data, it takes a looooot of time to even run a test migration.

@clacke @hexdsl @FediFollows @MarcellusDrum we have also migrated all but the main repo as well. There are PRs daily to Gitea project repos on we are very much in the dogfooding stage of things

@gitea @clacke @hexdsl @FediFollows @MarcellusDrum Is there an issue people can visit in regards to this migration effort?

Given the rate limit, perhaps there's a max project size that orgs can be mindful to migrate before they get to it.

@weex the PR with regards to using multiple tokens is: Gitea is one of the top 500 repos on GitHub (issues, PRs, comments, stars, etc…) it is an extreme edge case. The migrations can be done with one key, and we’ve had a mostly successful migration that way, but we’d risk a GH outage meaning we’d need to start again because it’s taking so long, and because of the time we’d probably need to lock contributions so that no new issues or PRs are submitted during transfer.

Sign in to participate in the conversation

A newer server operated by the Mastodon gGmbH non-profit