This is a great view into how you approach database CI. Thank you!
How do you manage code reviews after code is deployed to the Development environment?
Thanks, Data Wrangler! I'm glad you liked it.
Generally, the engineer will generate a Pull Request for his/her feature branch against the Test branch; our definition of done for Test says that you need at least one approval before you can merge (Bitbucket can be set up to enforce this). This is a bit of a departure from standard GitFlow where you'd promote Dev in its entirety. But because our dbs are shared across several apps, and our Product Owners don't always approve an entire Sprint's worth of work for immediate release, we need to promote at a feature granularity.
That sounds like just the approach we should use, and we happen to have Bitbucket Server. We too, have databases shared by multiple applications, so we'll probably go with feature branches. Now if only we can get our hands on Red Gate SQL Source Control--it's been a struggle budget-wise recently.