Sure thing. Devs develop locally. Can test their code (manual test and most automated tests). They push and open a PR. They can deploy ephemeral environments

Sure thing. Devs develop locally. Can test their code (manual test and most automated tests). They push and open a PR. They can deploy ephemeral environments with any dependent microservices spun up along side. This is an in house tool we developed that builds and deploys ephemeral docker, CDK, and terraform based apps. We then run CI automation against their PRs. This can include E2E tests courtesy of these ephemeral environments. Once their PR is green and signed off, they merge to master. We’ve done some wizardry behind the scenes so that their code is live in production in around 3 minutes. They verify their changes in prod and we run any automated regression tests against prod. Next person merges as they see fit. That’s it! It’s not easy to get to that point, but once you’re there it’s a great process. We’ll have capacity issues once we get up to 30 or 40 releases per day in a repo, but I’ve got some ideas about how to work around that.