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
For a less popular repo, the master build could be in failed state for prolonged period without being noticed.
E.g. a 25 day failure here. This build failure is caused by a core change and we should have caught and fixed this problem early on vs now being notified by a bug report.
So a feature request: miq-bot to notify (e.g. by emailing) maintainers after say failure not fixed within 1 day.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not been updated for at least 3 months.
If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.
Thank you for all your contributions! More information about the ManageIQ triage process can be found in the traige process documentation.
For a less popular repo, the master build could be in failed state for prolonged period without being noticed.
E.g. a 25 day failure here. This build failure is caused by a core change and we should have caught and fixed this problem early on vs now being notified by a bug report.
So a feature request: miq-bot to notify (e.g. by emailing) maintainers after say
failure not fixed within 1 day
.The text was updated successfully, but these errors were encountered: