Replies: 1 comment
-
|
The message “This job failed” does not provide meaningful or actionable information for most users. While detailed logs may exist elsewhere, users should not have to navigate away from the deploy screen just to understand why a job failed. It would greatly improve usability if the deploy screen displayed a brief, human-readable reason for the failure—such as the failed step, error type, or a short summary—along with a link to detailed logs. This would reduce troubleshooting time and keep critical feedback visible and contextual within the workflow. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Why are you starting this discussion?
Question
What GitHub Actions topic or product is this about?
Workflow Deployment
Discussion Details
Yes, I personally am well aware of the details, but normal humans won't be. The gray box should have useful information. You shouldn't have to go to a screen other than the screen with the ❌ deploy to find out "Why This job failed".
Yes, there are technically Annotations, but they're invisible to a normal user.
Annotations
Annotations
2 errors
❌ Branch "main" is not allowed to deploy to github-pages due to environment protection rules.
❌ The deployment was rejected or didn't satisfy other protection rules.
Beta Was this translation helpful? Give feedback.
All reactions