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.
@fediversenews@venera.social #fediverse #GitHub #git
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.
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.