04/04/2025
🔍 How We Keep Our Codebase Stable at Playrix
We're continuing our series on how development processes are organized at Playrix. Today, let’s talk about how we maintain a green master—a stable codebase that keeps development smooth and ensures game quality.
💡 Why does this matter?
With hundreds developers working on a game across iOS, Android, Windows, Mac OS, and Web, keeping the codebase stable is no small feat. But at Playrix, this process is well-structured, standardized, and optimized.
Our Multi-Level Quality Control System
1️⃣ The First Checkpoint: Pre-commit Hooks
Before any changes are made, we run automated static checks. These take just 10 seconds on average, allowing developers to catch and fix issues before creating a pull request.
2️⃣ Pull Requests & Testing Budget
Once the pre-commit checks pass, a pull request is created—but merging it into the main branch is blocked until a full round of builds is completed. These builds verify that the game runs smoothly across platforms and must fit within a 1-hour budget. Initially, this process took 2 hours, but we've optimized it to 40 minutes for most cases.
3️⃣ AI + Code Review
Every change goes through an AI assistant, which scans for potential issues. Then, a human reviewer assesses the code for scalability, clarity, and long-term maintainability.
4️⃣ Nightly Checks & Auto-Detection of Bugs
Even after a merge, the verification process isn’t over. Nightly quality gates run additional tests that wouldn’t fit into the pull request budget.
If an issue is detected, an automated bisect identifies the exact pull request that caused it and assigns a task to the responsible developer.
The bottom line: Our multi-layered verification system allows us to ship high-quality games while maintaining speed and a great developer experience.