Update dependency rubocop-github to "~> 0.26.0" - abandoned #8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
"~> 0.17.0"->"~> 0.26.0"Release Notes
github/rubocop-github (rubocop-github)
v0.26.0Compare Source
v0.25.0Compare Source
v0.24.0Compare Source
v0.23.0Compare Source
v0.22.0Compare Source
v0.20.0Compare Source
>= 1.37), "rubocop-performance" (>= 1.15), and "rubocop-rails", (>= 2.17).v0.19.0Compare Source
DisabledByDefault: trueinconfig/default.yml. Prevents confusing behaviour where users of the gem didn't realise that RuboCop's default cops weren't being applied (including potentially custom cops in their projects). We've explicitly setEnabled: falsefor all the cops that were previously default disabled. This has the effect that consumers of this gem won't be surprised by new linting violations when they use this new version in their projects. (https://github.com/github/rubocop-github/pull/119)v0.18.0Compare Source
Cop::BaseAPI instead of the deprecatedCop::CopConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.