Epic: GitLab Integration v1

[asaphko]

Flagsmith integrates with GitHub for issue/MR linking and Code References. This epic adds the same for GitLab, including self-managed instances.

Scope

Two workstreams:

Project integration — link GitLab issues and merge requests to feature flags. When a linked issue or MR changes state, Flagsmith auto-tags the feature and posts a comment with the current flag state. Authentication via Group or Project Access Tokens, not tied to individual users.

Note

A vibe-coded prototype already exists and is under review.

• feat: Add GitLab integration for project-level repository linking #7028
• feat(gitlab): add GitLab API v4 client with typed responses #7120
• feat(gitlab): add configuration persistence and resource browsing #7121
• feat(gitlab): add webhook handling, tagging, and shared VCS module #7122
• feat(gitlab): add frontend components for GitLab integration #7123

Code References — let GitLab CI scan repositories for feature flag usage and report results to Flagsmith. Reuses the Python scanning tooling from Flagsmith/ci, delivered as an include:remote template.

Open questions

Should we support Group Access Tokens to avoid per-project configuration? A group token covers all projects in a GitLab group, so we could offer organisation-level integration on the Flagsmith side. On gitlab.com, group tokens require Premium or Ultimate (any licence on self-managed). Free-tier users on gitlab.com are limited to Project Access Tokens (one project) or Personal Access Tokens (all projects the user has access to, but tied to an individual).

Out of scope

• CI/CD Catalog component — requires a project on gitlab.com. Can be added later without breaking the include:remote path.
• OAuth flow for GitLab authentication.