chore: create separate CI jobs for linting and testing #56
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.
Removes the linting step done in the
npm test
script. Instead, we run a separate CI job that handles just the linting checks so that it doesn't potentially interfere with tests running.So now we have two jobs that run in our CI workflow:
Could potentially argue that TypeScript checks should live in (1), but I think it's fine to keep in (2) for now, which aligns with how we have other repos set up.