GitHub Community
-
|
I recently introduced an error in a workflow file in a PR but neglected to notice as the PR showed as green and passing all checks (it just hadn’t run the jobs from that workflow). It would be nice to surface invalid workflow files as a failing PR check so that it it is less likely that they will be missed. Some other CI systems report this an on “error” rather than a “failure” to distinguish them. Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments
-
|
Thank you for your feedback - we appreciate it and will pass it on to the Product team. For future reference – we really appreciate feedback on how we can make GitHub even better and the best way to report any feature requests is directly to us through our feedback form: https://support.github.com/contact/feedback Our roadmap is not publicly visible, so we recommend that you keep an eye on the GitHub Blog for the latest announcements about new features. |
Beta Was this translation helpful? Give feedback.
-
|
It’s been about a year since this was brought up. Is this still on the radar? An invalid workflow file should show up as a failure in PR/push checks. Show the green “all checks passes” when your workflow itself has failed is clearly misleading and erroneous. |
Beta Was this translation helpful? Give feedback.
-
|
I have same question? I can not find a fix for this. It makes catching problems very difficult and could allow a merge to happen that should not happen. I would think that this should have been a high priority to fix. |
Beta Was this translation helpful? Give feedback.
-
|
maybe the  GitHub - nektos/act: Run your GitHub Actions locally 🚀Run your GitHub Actions locally 🚀. Contribute to nektos/act development by creating an account on GitHub. you may be able to run that in “dry-run” mode as part of a PR checker and then flag the PR as valid or not according to the output. I don’t know the specifics of any of this but I wanna help, and this seems like it can help. |
Beta Was this translation helpful? Give feedback.
Thank you for your feedback - we appreciate it and will pass it on to the Product team.
For future reference – we really appreciate feedback on how we can make GitHub even better and the best way to report any feature requests is directly to us through our feedback form: https://support.github.com/contact/feedback
Our roadmap is not publicly visible, so we recommend that you keep an eye on the GitHub Blog for the latest announcements about new features.