Specify project and branch and ENV when communicating

This is part of the Semicolon&Sons Code Diary - consisting of lessons learned on the job. You're in the collaboration category.

Last Updated: 2021-05-15

During Project S, we had a mobile app and a backend application in distinct repos. We had master and development branches. We had production and staging deploys. And we had local, staging, and production environments. All of these got confused with one another in communicating, because I might assume staging and Y might assume local etc.

Therefore the best practice was to specify all these parameters in comms. I.e. - repo - branch - env