CI Runners
Coming (phase 3)GitHub Actions jobs, moved by changing one line: their runs-on.
Integrations
Each product speaks its provider's language: pull requests and checks on GitHub, merge requests and pipelines on GitLab. GitHub comes first in each product.
Install the ohmakohq GitHub App on an organization; a personal account can't install it. Then move a GitHub Actions job by changing its runs-on to an ohmako- label, such as ohmako-ubuntu-latest-x64-2x.
Each job's runner registers in the organization's Default runner group with only that label, so a job meant for your own self-hosted runners never lands on ours.
GitHub Actions jobs, moved by changing one line: their runs-on.
Reviews in the pull request: inline findings, replies in the thread, and the Autofix button. Reading the code and pushing fixes needs Contents: write and Pull requests: write on the repositories where you turn it on.
Queues pull requests and merges them in order, with each one's place and status in the pull request. It works with branch protection.
Jobs start from a prepared snapshot, warm, instead of setting up from scratch.
Machines that check out your repositories, several to one environment if you need them.
Reads your GitHub Actions history and workflows, read-only by default.
Tests each pull request's change against a copy of your app, and comments its findings on the pull request.
Code Review and Merge Queue come to merge requests as the last milestone of phase 4, in GitLab's own terms. CI Optimization reads GitLab CI as well as GitHub Actions, and GitLab CI runners come in phase 9.