Oh for sure; there's significant work to be done before it's remotely merge-able, hence the "WIP" and "Draft" status. I'm not sure when I'll be in a position to do more than I have already, but wanted to at least share the progress of bringing the previous PRs up to a state where they at least compile and run on the current code-base.

Thanks for the direction in your comments, though; that will certainly make it easier to make a start on this. :)

Any thoughts on Forgejo vs Gitea? Looks like they should be basically compatible, and have a good amount of momentum behind them.

Software-wise they're currently identical since Forgejo is a soft fork.

They're very much compatible at the moment; Gitea clients will work perfectly with Forgejo servers.

I do know some of the people behind Forgejo are also some of the people behind ForgeFed and they're putting a lot of effort into implementing it. If I remember correctly, the primary Gitea maintainers were pretty ambivalent to federated forges, so I can definitely see them diverging in that area further down the line.

To complete the git issue/PR graph: this address issues #349 (bridge), part of #80 (integration). And has related issue on the gitea side at go-gitea/gitea#6519

I've had a little time this weekend to poke at this, and have started adding some unit tests (based on those for the Github/Gitlab bridges) to make this easier to develop. Given I'm still learning the language, I figure having a test harness is a particularly good way to proceed. Not sure how far I'll get with the time I have, but… small steps!

This bot triages pull requests in order to help the maintainers
identify what needs attention, according to the following lifecycle
rules:

• After 90 days of inactivity, lifecycle/stale is applied
• After 90 days of inactivity since lifecycle/stale was applied,
  lifecycle/rotten is applied

This bot will not automatically close stale pull requests.

To remove the stale status, you can:

• Remove the stale label from this pull request
• Comment on this issue
• Close this issue
• Offer to help out with triage and code review

To avoid automatic lifecycle management of this pull request, add
lifecycle/frozen.

̇

Github stale bot considered harmful

(Doesn't apply as long as the bot isn't configured to close everything after it becomes ''''rotten'''')

thank you for all of the hard work that's been put into this so far. i'm going to close this for now to help keep the active board clean, but am in no way rejecting the feature suggestion -- this has just been inactive for a long time.

if you wish to address the feedback and submit an update, you can always check out this tree like so:

$ git fetch https://github.com/git-bug/git-bug.git refs/pull/1077/head
$ git checkout FETCH_HEAD

feel free to ping me in a comment here to reopen the PR (to avoid needing to create a new one).