Conversation
|
@pwalczysko it is looking like
There is no preview currently in this repo (pending #9). I'll set that up on mine for now and write the code to do it here. |
Great, thank you, I like it. This is stricter than before, but it makes perfect sense to me. I mean for example the below is (in the sense of what I am suggesting) now green, although the scheduled workflow runs are definitely still FAILED:
But if the above suggestion is too tricky to implement, then better leave it at this very strict state rather than reporting a false "SUCCESS". Thanks a lot for this, I got quite used to this board. |
|
Thank you, @pwalczysko. For the snapshot, I am currently mocking the behaviour of the failure, but the new code may be doing what you say, if I got it correctly: The workflow id is the same regardless of triggers (scheduled, push, workflow_dispatch etc), so the code reports the last status. Currently, it gets a SUCCESS report for If a repository has multiple workflows (each with multiple runs), the dashboard will signal first any FAILURE, then any PENDING and only show SUCCESS if all latest runs look fine. I've tested it now here and the automatic run updated it from "FAILURE" to "SUCCESS":
|
|
Now, as for behaviour, currently it reports a FAILURE if either the last commit OR the last workflow run failed. Consider this situation:
I think the dashboard should display SUCCESS in those cases. So the last run is the source of truth for visual display. I'll add a commit to that. |
Agreed. Thanks. |
- Status reports visually the sum of the _workflow_ runs - Even if there are no _checks_, SUCCESS in workflows like dependabot will produce a green mark. - A tooltip signals if the workflow_run and last_commit checks differ.
🌐 Preview DeploymentPreview URL: https://ome.github.io/status/pr_preview/14/ Deployment is in progress and should be available shortly. |
|
The PR Preview is available at https://ome.github.io/status/pr_preview/14/ Here is one example of it in action:
It is giving it a red flag because of:
It is ~1y old, but it is listed by GitHub as (1) an "active" workflow, for (2) which the latest result was a failure. Would you benefit from any UI changes or anything different there? |
Thanks a lot @lubianat for this nice help on review. Lgtm |






Fixes #13