You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GitHub Actions regularly (every few months) drops support for specific Python versions. There are likely other unstable aspects of the build environment. Given this, a badging saying "passing" for a build that hasn't run for months is rather meaningless. Add a regular job (e.g. a weekly build) that sanity-checks the build against the current environment. This will definitely fail at some point after the project is no longer under active development, but this seems preferable to pretending that it builds correctly, even though a build may not have run for weeks or months.
The text was updated successfully, but these errors were encountered:
GitHub Actions regularly (every few months) drops support for specific Python versions. There are likely other unstable aspects of the build environment. Given this, a badging saying "passing" for a build that hasn't run for months is rather meaningless. Add a regular job (e.g. a weekly build) that sanity-checks the build against the current environment. This will definitely fail at some point after the project is no longer under active development, but this seems preferable to pretending that it builds correctly, even though a build may not have run for weeks or months.
The text was updated successfully, but these errors were encountered: