Forget Mono vs. Multi-Repo: Building Centralized Git Workflows for All Apps
summary
Demonstrates a working centralized CI pattern that listens to PR webhooks, uses a GitHub App + dispatch workflow to trigger a single central pipeline stored in one repo, and runs that pipeline with GitHub Actions. Implementation is Python (async with aiohttp + ngrok for local testing) and a GitHub API wrapper (gitjethub in demo). Solves duplicate CI files by creating remote checks via the Checks API and posting results back to PRs; initial visibility gaps are fixed and the team reports large CI/CD velocity gains.
AI-written summary · about
chapters (8)
- 0:00Start
- 1:18Cl in Mono vs. multi repositories
- 5:24Creating the Github Application
- 16:28Centralized Cl overview with status
- 16:51Modifying the CI job to create & update checks
- 17:08Centralized Cl architecture with status
- 23:59What did we not talk about here?
- 26:42Centralized Cl at Jit running security tests
related talks
15mCentralized CI Monitoring with GitHub Actions
16mHow We Moved to a Monorepo
22mMonorepo - One Repo To Rule Them All
37mGitHub Actions + K8S to level up software dev
23mMulti-Cloud Deployments with GitHub Actions
20mSetting up and managing GitHub actions for multiple projects
43mGitHub Actions Best Practices
36mPutting an End to “Isn’t this the Same Root Cause as That Project Six Months Ago? Why Didn’t You Prevent It?” — Reusable Workflows …