Skip danger check on documentation MRs
What does this MR do and why?
While testing the release tooling for the maintenance policy, it was
noted documentation MRs fail with a Danger check !112612 (comment 1287284700). The check validates merge requests targeting stable branches have the type::bug
label, for
documentation changes it shouldn't be required to have the label because
doc updates are not bug fixes. This commit skips the danger check on
documentation merge requests.
Related to gitlab-com/gl-infra/delivery#2839 (closed)
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by Mayra Cabrera