Erlend Sogge Heggen (@[email protected])
writing.exchange
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
  • fer0n@lemm.ee
    13·
    1 year ago

    So that people can follow the PRs for a certain project? Or what’s the use case for this

    • Gamma@beehaw.orgEnglish
      37·
      1 year ago

      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

      In the most expansive version of this vision, anyone running an AP-enabled git instance (with one or more repos) can send MRs to another instance’s repo, without having to sign up there.

      source

      • fer0n@lemm.ee
        19·
        1 year ago

        Thanks :) So since Gitlab can be self hosted there wasn’t a way to make PRs from one instance to another?

        • Gamma@beehaw.orgEnglish
          18·
          1 year ago

          Yeah, each server was separate but this helps their users connect between them without signing up. Also apparently Gitea is adding similar support