Several years in the making, GitLab is now very actively implementing #ActivityPub! 🙌
https://gitlab.com/groups/gitlab-org/-/epics/11247
The end-goal is to support AP for merge requests (aka pull requests), meaning git.alice.dev can send a merge request to gitlab.com/Bob/project.git
First bite-sized todo on the implementation path there is ‘subscribe to project releases’.
Smart move by #GitLab; through ActivityPub they’re getting a distributed version of GitHub’s social layer.
@
[email protected] #fediverse #GitHub #git
Github is pretty annoying nowadays - and pretty much the only reason I haven’t left for my own stuff is because going to a different platform will probably see me in the same situation in a few years again.
I still have my self hosted git instances around, and everything is pushed to there plus github - but github is where issues get created and pull requests come in as obviously nobody wants to make yet another account. That might be able to solve just that.
Gitea is also claiming to work on ActivityPub soon as well.
Yeah, this is huge.
It makes self hosting projects others will interact with actually realistic. And, assuming they support forks at some point, migration and backups should be easier than some of the other federated platforms.
I have a self hosted Forgejo instance with disabled user registration. The problem is as you mentioned ,- nobody wants to create yet another account. What’s more, it’s not possible to create PRs using e-mail.
I’d have to give out my e-mail somewhere on the git page then say “send patches here”.
It’s somewhat wise to disable user registration because users can freely fork your repos within your instance then change the fork to host whatever they want.