Tweak behaviors of build and release CI workflows #621
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.
Hello! With this PR I've tweaked some settings that @xylar and I have determined work out better in CI workflows on other repos. I've made the same changes here. These changes include:
cancel_others
is now set to false by default, which should make it easier to decipher if a bug is isolated to a specific version of python via CImamba
/mambaforge
have been removed and/or changed toconda
andMiniforge3
pre-commit
job has been upped to 5 minutesUpdated template from @forsyth2
Issue resolution
This pull request is a minor adjustment that does not affect functional code.
1. Does this do what we want it to do?
Objectives:
Miniforge3
rather thanmamabforge
cancel_others
is now set to False.Required:
2. Are the implementation details accurate & efficient?
Required:
3. Is this well documented?
Required:
4. Is this code clean?
Required: