Thanks for the insights. Unfortunately, I don't think running tests after PR is merged would be acceptable for our team. We have a similar release process, too, but even if it doesn't affect production users, it will break the main branch and disrupt the workflow of other engineers in the team if they rebase the broken main code. We also experienced issues in the past where integraiton test passed locally but failed on GitHub due to bad environment configuration. I'm concerned that PRs will revert frequently. It will save a lot of costs. Comparing that with engineering time for reverting and debugging, it's an interesting tradeoff 🙂