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
Opening an issue (from an accredited reporter) would add a notice on status.jenkins.io, and its closure comment would be the final message of the notice, closing it at the same time.
To be coupled with issues template to set a form with services & severity levels
Only publish issues with a specific label
Pin actives/unresolved issues
How to review these publications? Add the label via a PR? (Cumbersome, can't see the notice body directly, ...?)
The text was updated successfully, but these errors were encountered:
issue form template, with issue body as content and commit msg as new filename in ./content/issues/?
creation of the file with a GHA
the attribution of a specific label could trigger the creation of a new PR (with link to the issue as "related") to be reviewed?
closing the related issue would trigger the creation of another PR with final message (closing issue comment? [force a comment to close an issue here and in helpdesk?])
Upptime (upptime.js.org) is the open-source uptime monitor and status page, powered entirely by GitHub Actions, Issues, and Pages. It's made with 💚 by your friends at Koj.
I find Upptime an incredible clever usage of [GitHub Actions]. You essentially get a free configurable uptime monitor for whatever you want. – CSS Tricks
Upptime is used by 1,000+ people and teams to ensure they know when their endpoints go down.
Opening an issue (from an accredited reporter) would add a notice on status.jenkins.io, and its closure comment would be the final message of the notice, closing it at the same time.
To be coupled with issues template to set a form with services & severity levels
Only publish issues with a specific label
Pin actives/unresolved issues
How to review these publications? Add the label via a PR? (Cumbersome, can't see the notice body directly, ...?)
The text was updated successfully, but these errors were encountered: