When you are actively contributing across multiple large-scale open-source repositories—like gitlab-org/gitlab (Ruby on Rails), gitlab-lsp (TypeScript/Go), and ai-assist (Python)—context switching is the biggest bottleneck.
Between checking maintainer emails, stripping out unwanted lines of code, satisfying rubocop / danger-review / ruff , and babysitting long CI/CD pipelines just to hit "Start Merge Train" , hours of engineering focus get lost to manual admin work.
So, I built a Zero-Touch Autonomous Pipeline :
GitLab Mail + Antigravity IDE + CodeRabbit + glab CLI = Clean Code Directly on the Merge Train
Here is the exact step-by-step guide on how this workflow operates, what to do once the agent links your GitLab session, and how you can replicate it for your own open-source contributions.
🏗️ The Architecture: How the Loop Works
Instead of manually reading emails, switching branches, running linters, and replying to threads, the entire lifecycle is delegated to an autonomous agent inside Antigravity…