Keboola
Day 17 after signup
So… who else has ever tested code in production?
Merge requests are live in your projects today.
Why it works
- Open with a familiar pain point, then quickly explain how the new feature addresses it.
- Organize practical instructions separately from caveats so readers can find both the first step and the operational details.
- Keep the call to action focused on a guide while leaving enough context in the email to make the feature understandable.
How it is built
- Production testing hook
- Feature workflow overview
- Steps to try it
- Important merge details
Email copy
Hi [First name], If testing in production is not your cup of tea, this one is for you. Now changes in a development branch go to production through a merge request. You see every changed configuration side by side with production, a teammate can review and approve it, and only then does it go live. It’s already in your project, nothing to switch on. Try it this week Next change to a production flow? Make it in a branch, open Changes, and click Send for review. Want nothing to merge without a second look? Turn on required approvals in Project Settings under Branch Protection. Working with Kai, Claude or Cursor? Ask them to open the merge request for you. The same flow works through the MCP Server and the Keboola Agent CLI. Good to know Only configurations are merged. It doesn’t add any tables from the branch, and the branch and its tables are deleted after the merge. Run the configurations in production to fill your production tables. Every merge creates a new configuration version, so you can always roll back. 👉 See how merge requests work Talk soon, Team Keboola LinkedIn | GitHub | YouTube | Instagram Privacy Policy | Manage Preferences | Unsubscribe © 2026 Keboola Czech s.r.o., Prague, Dělnická 27, Czech Republic