Smoke tests: add eslint-remote-tester-repositories
#1518
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Adds
eslint-remote-tester-repositoriesto smoke tests. Instead of maintaining separaterepositories.jsonit can be utilized from a centralized npm package. This package contains ~14K Github hosted repositories. I'm checking status of these repositories from time to time and release new versions. It is a separate package fromeslint-remote-testerfor easier releasing.Also:
GITHUB_ACTION. There's a default value to use now. feat: defaultgithub-tokentogithub.tokenAriPerkkio/eslint-remote-tester-run-action#5rulesUnderTesting: []. This is default value now. AriPerkkio/eslint-remote-tester@09c23ce