Skip to content
GitLab logoGitHub logo

Connect GitLab to GitHub

Move data between GitLab and GitHub the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

GitLab triggers
1
GitLab actions
2
GitHub triggers
14
GitHub actions
19

Automation ideas

What you can build with GitLab and GitHub

A few flows teams run between GitLab and GitHub. Use one as a starting point, or build your own from scratch.

  • New Project Issue Event in GitLab creates Create Issue in GitHub

    Triggers on project issue events when an issue is created or when an existing issue is updated, closed, or reopened.

  • New Pull Request in GitHub creates Create Issue in GitLab

    Triggers when there is activity on a pull request.

  • New Project Issue Event in GitLab creates Get issue information in GitHub

    Triggers on project issue events when an issue is created or when an existing issue is updated, closed, or reopened.

  • New Pull Request in GitHub creates Custom API Call in GitLab

    Triggers when there is activity on a pull request.

  • New Project Issue Event in GitLab creates Create comment on a issue in GitHub

    Triggers on project issue events when an issue is created or when an existing issue is updated, closed, or reopened.

  • New Star in GitHub creates Create Issue in GitLab

    Trigger when there is activity relating to repository stars.

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

Yes. Build one flow that starts in GitLab and acts in GitHub, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.