GitLab

Both expose REST and GraphQL APIs. GitLab supports mirroring GitHub repos for migration or backup.

GitLab for Slack provides merge request notifications, pipeline statuses, issue tracking. Available as native automation connector.

GitLab syncs Asana tasks with issues and projects with repos in real-time 2-way sync.

Figma integrates with GitLab for design-to-development handoff workflow.

Official GitLab plugin for all JetBrains IDEs. Manage MRs, browse issues, use GitLab Duo AI assistant.

Link previews for GitLab merge requests and issues inside Notion pages

Official GitLab Workflow extension. Create/review MRs, browse issues, run CI/CD pipelines from VS Code.

View development info (branches, commits, MRs) linked to Jira issues. Smart commits transition issues. GitLab for Jira Cloud app available.

Built-in node with action and trigger. Issue, repo, release CRUD. Trigger on Comment, Issue, Merge Request events.

Linear has a first-party GitLab integration that links Linear issues to GitLab Merge Requests and automates your issue status based on MR activity. When a developer opens or merges an MR that references a Linear issue ID in the title or description (using magic words like 'Fixes ENG-123' or 'Closes ENG-123'), Linear automatically moves the issue from In Progress to Done — no manual status updates needed. You can also copy a Linear-formatted branch name directly from the issue and use it in GitLab so the link is detected automatically. Setup requires a GitLab Personal Access Token or Project Access Token with at least read_api scope, plus a webhook configured in GitLab to send MR events to Linear. The integration supports both GitLab.com and self-hosted instances, as long as your instance is publicly reachable. Per-team workflow automations let different teams use different issue status mappings based on target branch or MR approval requirements. Data flows: GitLab MR events (opened, drafted, approved, merged, closed) flow into Linear to update issue status. Linear issue IDs flow into GitLab as linkback comments on MRs. Branch name suggestions flow from Linear to developers. Direction is primarily GitLab → Linear for status automation, with Linear → GitLab for linkback comments. Pain points: Self-hosted GitLab setup is more complex and requires the instance to be publicly accessible — internal-only instances won't work. Linkbacks post under the name of the token owner rather than a bot account, so Clockify recommends creating a dedicated Linear user for cleaner attribution. CI pipeline events for MR merge checks require additional webhook configuration. The integration cannot parse links from commit messages or MR comments — only from the MR title or description.

GitLab as Git provider for auto deployments. Preview deploys on MRs, production on main branch pushes.