ActivityPub

Introduced in GitLab 16.5 with two flags named activity_pub and activity_pub_project. Disabled by default. This feature is an Experiment.

On self-managed GitLab, by default this feature is not available. To make it available, an administrator can enable the feature flags named activity_pub and activity_pub_project. On GitLab.com, this feature is not available. The feature is not ready for production use.

Usage of ActivityPub in GitLab is governed by the GitLab Testing Agreement.

The goal of those documents is to provide an implementation path for adding Fediverse capabilities to GitLab.

This page describes the conceptual and high level point of view, while sub-pages discuss implementation in more technical depth (as in, how to implement this in the actual rails codebase of GitLab).

This feature requires two feature flags:

activity_pub: Enables or disables all ActivityPub-related features.
activity_pub_project: Enables and disable ActivityPub features specific to projects. Requires the activity_pub flag to also be enabled.

Most of the implementation is being discussed in an architecture blueprint, see this document for more information.

For now, see how to implement an ActivityPub actor.

Help & feedback

Docs

Edit this page to fix an error or add an improvement in a merge request.
Create an issue to suggest an improvement to this page.

Product

Create an issue if there's something you don't like about this feature.
Propose functionality by submitting a feature request.
Join First Look to help shape new features.

Feature availability and product trials

View pricing to see all GitLab tiers and features, or to upgrade.
Try GitLab for free with access to all features for 30 days.

Get Help

If you didn't find what you were looking for, search the docs.

If you want help with something specific and could use community support, post on the GitLab forum.

For problems setting up or using this feature (depending on your GitLab subscription).

Request support