Does Codowave Work with GitLab?
The honest answer: Codowave is GitHub-native today. It connects through the GitHub App, reads GitHub issues, and opens GitHub pull requests. If your team runs on GitLab or Bitbucket as the source of truth, Codowave isn't a drop-in fit right now. This page is straight about what works, what doesn't, and the options if you're on GitLab.
Start your 5-day trialWhat Codowave Supports Today
Codowave's whole model is built around GitHub as the source of truth for work:
- It reads GitHub issues and scores them for selection.
- It runs code in isolated containers and opens GitHub pull requests.
- It respects GitHub labels, branch protection, and CI status.
- The
@codowavePR-comment amendment flow runs on GitHub PRs.
This depth is deliberate — being GitHub-native is what lets Codowave treat your backlog as the queue. The trade is that the depth is GitHub-specific.
GitLab and Bitbucket: The Current Status
Native GitLab and Bitbucket support is not available today. We don't want to imply otherwise — a tool that claims integration it doesn't have wastes your evaluation time.
If GitLab support matters to your team, the most useful thing you can do is tell us. Demand from real teams is how integrations get prioritized. Reach out through the contact page and describe your setup (GitLab.com vs self-managed, team size, rough issue volume) so it counts toward prioritization.
Options If You're on GitLab Today
A few teams in this situation make one of these work:
- Mirror to GitHub. If you can maintain a GitHub mirror of the repo and route issue-to-PR work through it, Codowave operates on the mirror. This adds a sync step and isn't right for every team, but it's the most common bridge.
- Use Codowave on the GitHub repos you do have. Many orgs run a mix; Codowave can cover the GitHub side while you evaluate.
- Wait for native support and register interest. If mirroring isn't viable, registering demand is the highest-leverage move.