GitHub repo sync #307

We've got this org on GitHub that's several years old with dozens of repos and hundreds of issues, so the inertia is real.

I think many orgs/repos who'd like to make the move to tangled are in this position. It'd be nice if we could properly interact with the atproto-centric side of our community through tangled. GitHub actually has an API that allows for alternative interfaces to be built for its issues, which project management apps like Huly use to enable a two-way synchronization.

If we could set up mirrors for our main GitHub repos on tangled and have the Issues on tangled be a mirror of our GitHub issues, that'd avoid the information fragmentation that we see happening in mirrored projects like Leaflet, which has distinct issues on tangled and gh, which will lead to a lot of duplicates over time:

In addition to the API interfacing, for this to work well it'd require two other key featues:

Per-user GitHub connection, for those who want to engage with a mirrored gh repo via their own gh account.
A tangled bot on GitHub that can post on behalf of tangled users who don't have a gh account.

This would be a good way to seed a tangled space with content before it's a project's canonical code forge. Once the stars and overall activity on tangled is growing apace with GitHub it becomes a lot easier to justify a permanent switch.

This is something I'd be happy to pay for as an org, especially if the mirroring itself could also be automated by tangled. The sync setup flow I want would be:

Enter org
Authenticate with GitHub (as org owner)
Select repos to sync
Install tangled app/bot on GitHub