Add settings option to menu and use Ruby 2.1.10 in Travis #1899
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.
What does this implement/fix? Explain your changes.
This adds an option to the Packages -> Atom Beautify submenu, Settings, that goes directly to the settings page for Atom Beautify. This is also available in the command palette.
During the initial Travis build, Rubocop could not be installed on the OSX build because it requires Ruby 2.1 or greater. The default is 2.0.0, thus a second change was added to use Ruby 2.1.10 so that the Travis build would pass (although it didn't fully, more on that below).
...
Does this close any currently open issues?
#1869
...
Any other comments?
The OSX Travis build will still fail. I'm getting the same errors with puppet-lint and sass as the master branch here. I'm still working with Travis support to try and resolve them, but the builds will continue to fail for now. Since it doesn't fail until the very end, and the Linux builds are fine, it should be safe to merge IMO.
...
Checklist
Check all those that are applicable and complete.
master
branchnpm run docs
CHANGELOG.md
under "Next" section