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.
The concurrency field prevents multiple instances of the same
workflow (or any two workflows with the same concurrency value) from
running at the same time. It will also cancel/replace pending workflows
when the new one attempts to run. That could put us in an edge case
where a PR test run could be skipped, but I think a skipped test run is
probably better in the long run than a failed test run. In either case,
this should not affect any active workflows.
I've added individual concurrency groups for the test, versioning,
documentation, and publication stages. The PR check workflow is simple
enough that it shouldn't have any problems running concurrently, but we
can always revisit in the future.
Types of changes
to change)
Checklist:
eslint
on the codePriority:
Related Issues:
Fixes #521