Danger can enforce existence of closes trigger
In https://gitlab.com/gitlab-org/release/docs/blob/127b2d01a3f38584bf4861361dfa37727f9e4294/general/deploy/auto-deploy-transition.md we've highlighted the need to not close an issue before the change is verified through different environments.
The reason for this requirement is that issue indicates whether the work is done or not. Work is not done until it is working at scale in production.
@andrewn suggested that we recognise this requirement with a Danger check that will look for "Closes", "Resolves" and "Fixes".
@yorickpeterse had a suggestion to instead of fail the pipeline right away, warn first and inform folks of the change in process.
I suggest that we consider doing this after https://gitlab.com/gitlab-org/release/framework/issues/368 is implemented.