Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When multiple runs exist for the same head, the action should consider only the latest #85

Open
Johennes opened this issue Mar 10, 2023 · 4 comments

Comments

@Johennes
Copy link

We're using the wait-on-check action for downstream tests. In particular this means the action is triggered from a commit in one repository and then runs the downstream tests using the current HEAD of another repository. This creates a problem because the action currently looks at all checks for that HEAD – including those triggered from previous commits to the first repository. To prevent that, I think the action should filter the checks so that only the latest one for each name / ID is taken into account.

@radnov
Copy link

radnov commented Oct 27, 2023

I'm experiencing the same issue.

@matiasalbarello I'm tagging you because you show up as the top contributor in this repo. Any ideas about this?

@t3chguy
Copy link

t3chguy commented Oct 27, 2023

@radnov you can try using my fork or commits if you like master...t3chguy:wait-on-check-action:master - no guarantees obviously

@radnov
Copy link

radnov commented Oct 27, 2023

Wow, thank you so much for the rapid and helpful response @t3chguy! Using the commit sha didn't come to mind ... 🤦

@dror-wing
Copy link

Thank you ! please consider merging it, this is a well needed feature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants