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.
This commit is contained in:
parent
1b9b67fa8f
commit
216e2493ed
1 changed files with 10 additions and 0 deletions
10
Dangerfile
10
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
|
||||
|
|
Loading…
Add table
Reference in a new issue