-
Notifications
You must be signed in to change notification settings - Fork 11
Revisit CI testing strategies #100
Copy link
Copy link
Open
Labels
ciImprovements or additions to CI checksImprovements or additions to CI checksconfigurationChanges to the configurationsChanges to the configurationshelp wantedExtra attention is neededExtra attention is needed
Metadata
Metadata
Assignees
Labels
ciImprovements or additions to CI checksImprovements or additions to CI checksconfigurationChanges to the configurationsChanges to the configurationshelp wantedExtra attention is neededExtra attention is needed
We need to revisit how to trigger the CI checks based on the events (
pull_requestvs.push), branches (main,staging, and the rest), and matrices (e.g., OS and Python versions).Potentially we could remove
tox, but then it might make sense to enforce the CI tests on everypushevent for all the branches. Currently CI tests is only enabled forpushtomainandpull_requestfor other branches.We also need to document the branching model and how it affects running the CI checks.