#Gitlab supports #ActivityPub in the upcoming 16.5 release. See links below for more details.

💬 "For GitLab, anything with activities (in the sense of what GitLab means by “activity”) can be an ActivityPub actor. This includes items like projects, groups, and releases. In those more abstract examples, an actor can be thought of as an actionable feed."

Documentation:
https://docs.gitlab.com/ee/development/activitypub/

Feature blueprint:
https://docs.gitlab.com/ee/architecture/blueprints/activity_pub/index.html

Merge request for the feature:
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/127023

ActivityPub | GitLab

GitLab product documentation.

Follow-up: #Gitlab released version 16.5 two days ago.

Edit: #AcitivityPub support is in the works. This means it will be possible to follow e.g. user activity or project releases with your #Fediverse account.

Thank you @kik for the clarification!

See the previous post in this thread and @kik's post below for more details and links on the extent of Github's AcitivityPub support.

Release announcement:
https://about.gitlab.com/releases/2023/10/22/gitlab-16-5-released/

GitLab 16.5 released with compliance standards adherence reports and merge request target branch rules

GitLab 16.5 released with compliance standards adherence reports, merge request target branch rules, improved fast-forward merge train support, resolvable comments in issues and much more!

GitLab

@floppy I'm sorry, it's not the case yet! We're quite far from it actually, there will be at least a few more months before we publish the first actor (allowing to follow project releases). You can follow the work here : https://gitlab.com/groups/gitlab-org/-/epics/11247 (most of the activity happens in issues/merge requests, mentioned at the bottom in the timeline).

GitLab always assign the tickets to the next milestone (thus next GitLab version), but it's just because there is no deadline for this work, when a new release happens, they move the ticket to the next milestone.

Rest assured that we'll let everyone know here when we release something ready to use! :) Chances are we will do a progressive rollout at first, though, allowing a few instances at a time, then more, to be able to measure the load and make sure it does not disrupt other GtiLab services.

Support ActivityPub for GitLab (#11247) · Epics · Epics · GitLab.org · GitLab

Gitlab/ActivityPub Design Documents by @oelmekki The goal of those documents is...

GitLab
@kik Thank you for explaining details on Github's milestone plans! I updated to original post.
@floppy You're welcome. :) Thanks for sharing!