Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.
All Depfu comment commands
@depfu rebase
Rebases against your default branch and redoes this update
@depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@depfu close
Closes this PR and deletes the branch
@depfu reopen
Restores the branch and reopens this PR (if it's closed)
@depfu pause
Ignores all future updates for this dependency and closes this PR
@depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ rubocop-performance (1.15.1 → 1.15.2) · Repo · Changelog
Release Notes
1.15.2
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 17 commits:
Cut 1.15.2Update ChangelogUse RuboCop RSpec 2.16Merge pull request #321 from koic/fix_a_false_positive_for_performance_sumFix a false positive for `Performance/Sum`Merge pull request #315 from koic/fix_a_false_negative_for_performance_redundant_string_charsMerge pull request #317 from rubocop/dependabot/github_actions/actions/setup-python-4Merge pull request #319 from fatkodima/string_include-not-matchExtend `Performance/StringInclude` to handle `!~`Merge pull request #320 from fatkodima/regexp_match-regexp-cbaseFix `Performance/RegexpMatch` to handle `::Regexp`Bump actions/setup-python from 2 to 4Merge pull request #316 from ydah/dependabotAdded dependabot for GitHub Actions[Fix #313] Fix a false negative for `Performance/RedundantStringChars`Use RuboCop RSpec 2.15Switch back docs version to masterDepfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands