Skip to content

Chore: set danger-review to no-needs

Lucas Charles requested to merge set-danger-to-no-needs into master

What does this MR do?

danger-review stage doesn't rely on the output of previous stages. By setting needs: [] the job can start immediately and provide feedback much more quickly, see docs: https://docs.gitlab.com/ee/ci/yaml/#needs

What are the relevant issue numbers?

Does this MR meet the acceptance criteria?

Merge request reports