GitLab

Powered by Zapier.

What is GitLab?

GitLab is where many teams host code and run their development workflow, repositories, branches, commits, issues, merge requests, and the CI jobs that build and ship. Working across it is a constant stream of actions: opening and updating merge requests, filing issues, branching, commenting, reviewing. This connection lets Fabric's assistant handle much of that for you, in plain language.

What Fabric's assistant can do with GitLab

Once your GitLab is connected, Fabric's AI assistant can act on your projects from plain-language requests.

Find merge requests. Find project, group, or all merge requests, so you can locate the work in flight without scanning projects.

Manage issues and merge requests. Create issues and merge requests, add notes to issues and merge requests, and update merge requests, the everyday triage and review work.

Work with code. Create branches and commits, so routine repo actions can be asked for rather than done by hand.

You describe what you want and the assistant maps it to the right GitLab action or trigger.

You stay in control

The assistant acts only when you ask. For anything consequential, creating a commit or branch, opening or updating a merge request, it confirms with you before going ahead, unless you've told it not to for a particular task. Finding and reading never change anything in your projects.

When something should happen regularly, you can set up a Fabric AI job that runs on a schedule, triaging new issues, commenting on merge requests, so the routine work runs itself while you keep approval over anything that changes code or merge requests.

Search your GitLab from Fabric

Alongside the assistant, connecting GitLab adds keyword search over your GitLab content from Fabric's main search, so an issue or merge request is findable by matching text in the same place you search the rest of your library, rather than searching GitLab separately.

How people use it

Engineers open and update merge requests, file issues, and create branches by asking, keeping the workflow moving without leaving their train of thought. It fits how Fabric works for developers.

Maintainers let repo activity, new issues, merge requests, review requests, trigger follow-on actions like commenting or notifying.

Teams running CI have job events trigger follow-up steps, so what happens in a pipeline can set something else in motion.

People with recurring repo chores set up a scheduled AI job to handle triage and review notes, while keeping approval over anything that changes code.

Frequently asked questions

What does the GitLab connection do?

It lets Fabric's AI assistant work across your GitLab, taking actions like creating and updating merge requests, filing issues, and creating branches and commits. It also adds keyword search over your GitLab content in Fabric.

What can the assistant do in GitLab?

It can find project, group, and all merge requests, create issues and merge requests, add notes to issues and merge requests, update merge requests, and create branches and commits. You ask in plain language rather than choosing from a fixed list.

Does the assistant change my projects on its own?

No. It acts only when you ask, and for consequential actions, creating commits or branches, opening or updating merge requests, it confirms with you first, unless you've deliberately told it not to for a specific task. Finding and reading change nothing.

Can I automate triage and review?

Yes. A Fabric AI job can run on a schedule, for example triaging new issues or commenting on merge requests, while you keep approval over anything that changes code.

Can I search my GitLab from Fabric?

Yes, by keyword, from Fabric's main search, so an issue or merge request is findable by matching text alongside the rest of your library.

How is this different from the GitHub connection?

Both work with code hosting and the development workflow; this one is for GitLab, built around merge requests, issues, and CI jobs. If your code is on GitHub, the GitHub connection is the equivalent. Choose the one your repos are on.

Is my GitLab data secure?

Everything in Fabric is encrypted in transit and at rest. The connection acts on your GitLab with your authorisation, and you control what it does. The details are in the privacy and security guide and Fabric's privacy commitment.

Does this work through MCP or the API?

Fabric also exposes your library and connected tools to external AI through its MCP server and API; this connection is the built-in way to have Fabric's own assistant work with your GitLab.

Does Fabric work with other tools alongside GitLab?

Yes. GitLab is one of many connections. You can also connect Notion, Google Drive, and Gmail, and automate across many apps with Zapier.