GitHub Community
Workflow on pull request doesn't show the last result #25574
-
|
I have a workflow which linting pull request title, format, and it is triggered when: When a pull request is updated, the workflow is triggered correctly, but having the following problems:
This behavior is not what I expect, may I know there is any way to adjust the result? Thanks. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
This would be the expected behaviour. Each trigger is logged and shown. It’s not that one trigger overwrites the other. You never want to lose sight of the history that happened on your workflow, otherwise debugging/testing would become very difficult. Plus if it would just start “hiding” things from you by overwriting previous runs, it would also complicate transparency when it comes to billing (where applicable). You would never be able to see where your build minutes would come from.
I don’t quite understand what you mean here. This would generally mean that your workflow failed, but without seeing any of your workflow or the output it generates, it’s hard to say. I’ve never seen this behaviour in any of my workflows before, so I don’t think this is a common bug or something that would be unexpected unless something actually goes wrong. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @oldskool thanks for your reply, for point 1, I can understand. For point 2, the pull request listing pages, I mean The red corss icon means the workflow failed, but it doesn’t change to a green check icon once the workflow runs successfully. It’s my idea that here it should show the latest status rather than fail always. Do you think it is possible? Thanks. |
Beta Was this translation helpful? Give feedback.
-
That is what should happen and what does happen for me. I’ve never seen it “stick” to a status after it changed. Maybe it’s a caching issue, but if you persistently see this and (hard) refreshing doesn’t help I think you’d best contact GitHub support about this. |
Beta Was this translation helpful? Give feedback.
That is what should happen and what does happen for me. I’ve never seen it “stick” to a status after it changed. Maybe it’s a caching issue, but if you persistently see this and (hard) refreshing doesn’t help I think you’d best contact GitHub support about this.