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

Docs: Ensure CLI doc sections match command line help order #10144

Merged
merged 3 commits into from Mar 29, 2018

Conversation

Projects
None yet
2 participants
@platinumazure
Member

platinumazure commented Mar 29, 2018

What is the purpose of this pull request? (put an "X" next to item)

[x] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofixing to a rule
[ ] Add a CLI option
[ ] Add something to the core
[ ] Other, please explain:

What changes did you make? (Give an overview)

Moved sections and options around in long-form descriptions of the CLI options to match the current sections and options as shown by node bin/eslint.js --help

Is there anything you'd like reviewers to focus on?

Not really.

@eslint eslint bot added the triage label Mar 29, 2018

platinumazure added some commits Mar 29, 2018

@platinumazure platinumazure changed the title from WIP: Docs: Ensure CLI doc sections match command line help order to Docs: Ensure CLI doc sections match command line help order Mar 29, 2018

@not-an-aardvark

LGTM, thanks!

@platinumazure platinumazure merged commit 65cc834 into master Mar 29, 2018

5 checks passed

commit-message PR title follows commit message guidelines
Details
continuous-integration/appveyor/pr AppVeyor build succeeded
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
licence/cla Contributor License Agreement is signed.
Details
release-monitor No patch release is pending
Details

@platinumazure platinumazure deleted the platinumazure-patch-1 branch Mar 29, 2018

@eslint eslint bot locked and limited conversation to collaborators Sep 26, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.