summaryrefslogtreecommitdiff
path: root/Dangerfile
diff options
context:
space:
mode:
authorLukas Eipert <leipert@gitlab.com>2018-09-07 13:20:06 +0200
committerLukas Eipert <leipert@gitlab.com>2018-12-17 09:58:39 +0100
commit243bd56f9db95a29deaec9ff093b2ff8d02f82ee (patch)
tree437d20ccde414ff8e9650283276bca0b6279a494 /Dangerfile
parent8b4602041cf2c4a8738a4796d78720017249249f (diff)
downloadgitlab-ce-243bd56f9db95a29deaec9ff093b2ff8d02f82ee.tar.gz
Add danger check for duplicate yarn dependencies
This danger check utilises `yarn-deduplicate` in order to show duplicate dependencies in the yarn.lock dependency tree. Often when introducing new dependencies or updating existing ones, yarn does not seem to build the most optimal dependency tree. In order to prevent those unnecessary dependency updates we are nudging developers and maintainers to resolve these issues in MRs. Automating this with danger especially helps, as yarn.lock files are not that easy to review.
Diffstat (limited to 'Dangerfile')
-rw-r--r--Dangerfile1
1 files changed, 1 insertions, 0 deletions
diff --git a/Dangerfile b/Dangerfile
index 469e77b2514..6a2c5cf2773 100644
--- a/Dangerfile
+++ b/Dangerfile
@@ -8,5 +8,6 @@ danger.import_dangerfile(path: 'danger/database')
danger.import_dangerfile(path: 'danger/documentation')
danger.import_dangerfile(path: 'danger/frozen_string')
danger.import_dangerfile(path: 'danger/commit_messages')
+danger.import_dangerfile(path: 'danger/duplicate_yarn_dependencies')
danger.import_dangerfile(path: 'danger/prettier')
danger.import_dangerfile(path: 'danger/eslint')