Closed kandersolar closed 1 year ago
I think running them once a week or so is a good idea. What's a good way to make test failures noisy enough to make us notice? I think it's possible to have a CI job open github issues. Maybe just emailing us is enough.
How about adding a cron schedule to the GitHub Actions? The below example would run at 00:00 every Sunday.
on:
schedule:
- cron: '0 0 * * 0'
In case of failure, wouldn't that email us? I think that should be sufficient - no need for a complicated workflow that creates an issue.
In case of failure, wouldn't that email us?
I don't receive email notifications for CI failures in any other job. Probably it's possible to get them somehow. I would only want to enable them if they can be enabled per repo or even per workflow though :)
I don't receive email notifications for CI failures in any other job. Probably it's possible to get them somehow. I would only want to enable them if they can be enabled per repo or even per workflow though :)
Good point - let's tackle this in another issue/PR since it's not time-sensitive and does not require a new release.
Thanks, @kanderso-nrel - you're a champ!
I think running them once a week or so is a good idea. What's a good way to make test failures noisy enough to make us notice? I think it's possible to have a CI job open github issues. Maybe just emailing us is enough.