Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix rubocop issues using --auto-correct #39

Closed
wants to merge 9 commits into from

Conversation

tchia04
Copy link

@tchia04 tchia04 commented May 30, 2019

This is for fixing all the issues reported by the most recent release of rubocop which is 0.71
rvm --create ruby-2.6.3@yamllint --ruby-version
$ rubocop --version
0.71.0
After --auto-correct
$ rubocop
Inspecting 13 files
.............

13 files inspected, no offenses detected

@@ -6,6 +6,7 @@ This file is used to list changes made in each version of the YamlLint gem.
- **[PR #28](https://github.com/shortdudey123/yamllint/pull/28)** - Fix Security/YAMLLoad rubocop offense
- **[PR #29](https://github.com/shortdudey123/yamllint/pull/29)** - Update TraviCI Rubies
- **[PR #30](https://github.com/shortdudey123/yamllint/pull/30)** - Fix Style/PercentLiteralDelimiters offense
- **[PR #39](https://github.com/shortdudey123/yamllint/pull/39)** - Fix trollop deprecation warning
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you copy the title of the PR from GitHub to here instead?

###
#
# YamlLint checks YAML files for correct syntax
module YamlLint
VERSION = '0.0.9'.freeze
VERSION = '0.0.10'
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please revert version bump as this will happen on the next gem release.

@shortdudey123
Copy link
Owner

Thanks for the PR!

Can you rebase on master and verify this still passes with the newest rubocop?

This was referenced Sep 23, 2021
@jamiemccarthy jamiemccarthy mentioned this pull request May 11, 2022
@shortdudey123
Copy link
Owner

Used #48 instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants