MR on a branch with no changes indicates it has been deployed to production
Today in GitLab there is a condition where an MR can show that it has been deployed to production, but in reality it is a brand new MR and branch that has simply had no changes.
This can lead to confusion as that branch was not actually deployed, even though that commit has been.
I believe this happens when the branch is at the same HEAD as what was last deployed to an environment. Perhaps we go by commit SHA to determine if something was deployed?
Design decision
- All other information including environment information should be hidden if the merge request widget empty state is active/visible.
Edited by Dimitrie Hoekstra