WIP: add --lkgr and --ulkgr options #552
Closed
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
add upadate task that will only run when --ulkgr option passed
Run on darwin
|
Closing, reopen if needed. |
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.
Added:
lkgrto the lookup (modules that passed on my mac).--lkgroption for citgm and citgm-all, which ranslkgrfrom the lookup, instead of defaulting to taking npm latest.--ulkgroption for citgm and citgm-all, to update lookupLet me know what you think and let's discuss if we want to include platforms flakiness for
lkgr.TODO:
Checklist
npm testpassesRefs: #407