From 216e2493edde7d9601fdb508a8835b93ec9d3c25 Mon Sep 17 00:00:00 2001 From: Nenad Vujicic Date: Mon, 4 Nov 2024 16:54:30 +0100 Subject: [PATCH] Added new Danger labeling rule Added new rule which checks if Gemfile is updated and Gemfile.lock is not updated and if positive generates "gemfile-lock-outdated" PR label. --- Dangerfile | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/Dangerfile b/Dangerfile index 3148bafb6..6e2aeced8 100644 --- a/Dangerfile +++ b/Dangerfile @@ -30,3 +30,13 @@ if git.commits.any? { |c| c.parents.count > 1 } else auto_label.remove("merge-commits") end + +# Check if Gemfile is modified but Gemfile.lock is not +gemfile_modified = git.modified_files.include?("Gemfile") +gemfile_lock_modified = git.modified_files.include?("Gemfile.lock") +if gemfile_modified && !gemfile_lock_modified + warn("Gemfile was updated, but Gemfile.lock wasn't updated. Usually, when Gemfile is updated, you should run `bundle install` to update Gemfile.lock.") + auto_label.set(pr_number, "gemfile-lock-outdated", "F9D0C4") +else + auto_label.remove("gemfile-lock-outdated") +end -- 2.39.5