Treat Gemfile and .gemspecs as Ruby #344
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
doomspork
approved these changes
May 14, 2019
doomspork
reviewed
May 14, 2019
sunny
commented
May 16, 2019
|
Thank you @sunny 😁 |
|
Thank you for the swift merge and for helping maintain pronto \o/ |
|
You're very welcome @sunny! I want to get a few of the other outstanding PRs merged and then cut a new release. If you're interested in lending a hand, I would greatly appreciate it 😁I'd love to grow the team of contributors |
apiology
pushed a commit
to apiology/pronto
that referenced
this pull request
Dec 27, 2019
* Treat Gemfile and .gemspecs as Ruby * Fix path of Gemfile
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 allows
pronto-rubocop(and others) to treat the commonGemfileand*.gemspecfiles as Ruby.