Skip to content

Danger checks for the frontend

Lukas 'ai-pi' Eipert requested to merge leipert-frontend-danger into master

What does this MR do?

This adds two Danger checks for the frontend:

  1. If you forgot to run prettier on one of the files you touched.
  2. It suggests to re-enable eslint rules if you edited a file which has a global eslint-disable in it.

Example output:

Screenshot_2018-09-25_at_16.43.22

What are the relevant issue numbers?

Does this MR meet the acceptance criteria?

Edited by Lukas 'ai-pi' Eipert

Merge request reports