Run CI tests weekly. - #1523
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1523 +/- ##
=======================================
Coverage 85.87% 85.87%
=======================================
Files 35 35
Lines 1883 1883
Branches 274 274
=======================================
Hits 1617 1617
Misses 187 187
Partials 79 79 Continue to review full report at Codecov.
|
matthiask
left a comment
There was a problem hiding this comment.
That is an excellent idea! The MySQL failures are definitely unrelated, something changed in the Django@main version...
(If you wanted to avoid too much load on Github you could switch to a weekly schedule but it probably doesn't make a big difference.)
Interestingly enough, that integration issue is exactly what this change is supposed to identify.
I added that because in the GitHub Actions documentation for It'd be ideal if we could schedule this to run when any of the tox dependencies has a release, but I'm not sure if that's really possible. |
This helps identify issues with the library as django and other dependencies release new versions.
|
I did a quick look on the interwebs for a way to trigger based on other packages releases, but the best option is dependabot. I think we could do this, but I'll open an issue for discussion. |
|
I also changed this to run weekly. It's more environmentally friendly and frankly we likely won't be fixing integration issues the day after the crop up. |
This helps identify issues with the library as
django and other dependencies release new versions.