Update CI pipeline so repeated commits don't cause concurrent tests #850
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.
I updated the CI pipeline such that if multiple commits have been made in relatively quick succession, the prior commit's in progress tests will be cancelled. Since the maggma tests take a fair bit of time, this is a nice convenience feature in my opinion.
I also updated the classifier for the production status to "Development Status :: 5 - Production/Stable" and added a missing
src
line in theruff
spec forpyproject.toml
.Note: I first learned about this from
repo-review
and have been using it for all my projects. You might be interested in some of the items flagged for maggma, although a fair number of them are quite subjective.