Context
From 2023 to 2025 I was the release and merge owner for the white-label learner app, a repo that took roughly 450 to 500 pull requests a year. I was not the architect of that app, and I do not claim to be. My role was the quality gate and the releases.
The problem
A busy repo with many contributors needed one consistent gate on what reached the main branch, and regular store releases and hot fixes for Android and iOS.
What I did
I performed the merge on most pull requests to the main branch: 57% in 2023, 67% in 2024 and 69% in 2025. In 2023 that was 232 of 404, in 2024 it was 251 of 373, and in 2025 it was 87 of 126.
I reviewed teammates' work: 216 pull requests in 2023, 283 in 2024 and 96 in 2025, about 600 reviews in all.
I ran store releases for Android and iOS, and set up hot-fix delivery with CodePush in 2021, re-enabled with staging and production scripts in 2022.
I added a code-owners file in late 2022 and built the CI pipeline and pod install steps.
Key decision
I chose to be one accountable gate rather than spread merging across many people. It made quality consistent, but it also made me a bottleneck.
Result
The headline is 57 to 69% of merges across three years, with about 600 reviews. In 2024 I merged 338 pull requests against 76 for the next person. Most merges into the repo passed through me.
I do not have release cadence or failure-rate figures, so I do not report them.
What I learned
I would again own the gate openly and keep release steps in scripts. I would spread merge rights sooner, and I would record release cadence so the effect of the gate can be measured.
Stack
- React Native
- Next.js
- GitHub
- CodePush
