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
I wrote a quick github action workflow that will run lint and tests for all the versions the previous travis one did.
I outlined some benefits in #272 to do this, as well as the need to get the CI working again for PR contributions.
About Github Actions
Once merged they will start running on all pushed commits to PRs.
I only added CI in this PR for introduction and to get it working on other PRs. It will run through a matrix of the node versions and perform both a lint/test on each. (maybe dont need to lint each version...)
About Github PR Template
Really simple, just provides a default PR description so you can structure how contributions are formed. It also facilitates notes that can help the PR reviewer.
The structure is markdown and i included 3 simple sections and invisible descriptions that are a good start. They can evolve over time depending on how you want to change them, but importantly having the file there allows others to change it.
Risk/Impact Analysis
Low Risk / Non-code changes
QA Notes
Setup a new workflow, or authorize me to setup the workflow in the settings of the repo.
We will need a followup ticket which i can outline in #272, which will publish to NPM on merges into main.