From fdc17ebc039e53dd0ed8119c92fac5fd2f43c7fe Mon Sep 17 00:00:00 2001
From: Ash McKenzie <amckenzie@gitlab.com>
Date: Mon, 26 Aug 2019 17:05:45 +1000
Subject: Add new danger_local Rake task

The benefit of running the danger_local Rake task
is that it displays some informational messages
for clarity and also exits with 1 if there's any
output.
---
 lib/tasks/gitlab_danger.rake | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)
 create mode 100644 lib/tasks/gitlab_danger.rake

(limited to 'lib/tasks/gitlab_danger.rake')

diff --git a/lib/tasks/gitlab_danger.rake b/lib/tasks/gitlab_danger.rake
new file mode 100644
index 00000000000..c2f5843a9a5
--- /dev/null
+++ b/lib/tasks/gitlab_danger.rake
@@ -0,0 +1,17 @@
+desc 'Run local Danger rules'
+task :danger_local do
+  require 'gitlab_danger'
+  require_relative '../../lib/gitlab/popen'
+
+  puts("#{GitlabDanger.local_warning_message}\n")
+
+  # _status will _always_ be 0, regardless of failure or success :(
+  output, _status = Gitlab::Popen.popen(%w{danger dry_run})
+
+  if output.empty?
+    puts(GitlabDanger.success_message)
+  else
+    puts(output)
+    exit(1)
+  end
+end
-- 
cgit v1.2.3