chore: add instructions on howto test specialized environments #3009
Conversation
This file contains hidden or 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
dariakp
requested changes
Oct 21, 2021
Co-authored-by: Daria Pardue <[email protected]>
dariakp
requested changes
Oct 27, 2021
Co-authored-by: Durran Jordan <[email protected]> Co-authored-by: Daria Pardue <[email protected]>
dariakp
pushed a commit
that referenced
this pull request
Nov 2, 2021
ljhaywar
pushed a commit
that referenced
this pull request
Nov 9, 2021
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.
Description
What is changing?
Adding some notes on how to test special environments.
What is the motivation for this change?
Adding documentation for environment variables is good to help figure out the intent. There is a risk of this document falling out of sync with reality if we don't maintain it, but having our intention documented now is helpful when someone comes back to look at how things work.
Double check the following
npm run check:lintscript<type>(NODE-xxxx)<!>: <description>