Document enabling --no-warn-script-location #6372
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
kx-chen
commented
Apr 1, 2019
kx-chen
force-pushed
the
document-no-warn-script-location
branch
from
5b6df6c to
7386587
Compare
chrahunt
reviewed
Oct 13, 2019
@chrahunt Sure, so just in the user guide then? |
Yep. |
pradyunsg
added
type: docs
chrahunt
reviewed
Nov 11, 2019
chrahunt
force-pushed
the
document-no-warn-script-location
branch
from
7386587 to
dd0ba3d
Compare
|
The RTD build is the only one failing so I'll merge this. Thanks a lot @kx-chen! |
chrahunt
approved these changes
Nov 11, 2019
lock
bot
added
the
auto-locked
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.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #6209
Minor change letting users know about
--no-warn-script-locationrequiring falsy values to be enabled