Chore: update issue template with --env-info flag #12352
Merged
Conversation
73cacd3
to
9ab2ece
|
Thanks for working on this! |
6ae6f6d
to
a44e1f5
|
\cc @kaicataldo |
|
LGTM. Thanks for contributing to ESLint! |
b718d2e
into
eslint:master
16 checks passed
16 checks passed
continuous-integration (Test on Node.js 12 (Windows))
Test on Node.js 12 (Windows) succeeded
Details
|
Thanks for contributing! |
This was referenced Nov 9, 2019
This was referenced Mar 26, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What is the purpose of this pull request? (put an "X" next to item)
[ ] 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
[x] Other, please explain:
updated the issue template accordingly such that it instructs the user to use
eslint --env-infoto find information converning his/her local environment.What changes did you make? (Give an overview)
v6.5.0release introduced a new--env-infoflag which would show up the local environment information. Updated the issue-template accordingly.Is there anything you'd like reviewers to focus on?
Nope