an idea: Github actions to sync to still have presence on github. GH issues will be sent to sourcehut via email. Repos is easily synced w/ git. Sourcehut mailing list posts can be forwarded as gh discussions.
@matthewp actually we might not need 'gh' -- I thought I'd need it to create a repo but apparently you can just push to a not existing repo and it will create it. They might have thought of enabling the common use cases with just git.
If you push to a non-existent repo in Sourcehut, it will create a new repo for you. The counterpart in Github is you need to first run "gh repo create" (which already a dependency).
I don't think we need federated forges with this workflow. You just need git and email. This is the way! (I mean, email is already federated by design)
Services are fine-grained and opt-in: if you just want a repo and no need for a bug tracker just dont create the tracker. If you somehow just need an issue tracker for a project that don’t have a repo, you simply create a tracker. That goes for all parts of the system it seems
Add comment