Automating cherry-picks between OSS and private forks

The Vitess project's private fork management was a challenge due to the need to stay aligned with upstream changes. Initially, a manual approach using GitHub Actions and Git replay was used, but it became unsustainable as the private diff grew larger. The team developed a new process with key requirements, including automating as much of the workflow as possible, ensuring continuous updates from OSS to private fork, and maintaining consistency across multiple release branches. A bot was created to automate this process, which uses GitHub Actions, a database instance, and stateful design to manage the workflow. The bot performs cherry-picking and backporting tasks, with integrity checks to ensure reliability. After implementing safeguards, the team rolled out the new process, saving hours of engineering time and allowing them to focus on innovative features.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.