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

Linter result gets attached to the wrong workflow #657

Closed
andreiz opened this issue Jun 8, 2023 · 1 comment
Closed

Linter result gets attached to the wrong workflow #657

andreiz opened this issue Jun 8, 2023 · 1 comment
Labels
duplicate This issue or pull request already exists

Comments

@andreiz
Copy link

andreiz commented Jun 8, 2023

I have 2 workflows running concurrently, build-and-test one and a linter one (using Apple's swift-format). The linter result (named swift-format) is being attached either to the linter workflow or to the build-and-test workflow, seemingly randomly.

This is how I expect it's supposed to be where the swift-format result is attached to my linter workflow job list.

Screenshot 2023-06-08 at 10 09 48

And this linter run does not have the result attached:

Screenshot 2023-06-08 at 10 09 06

But instead it ends up in the build-and-test workflow:

Screenshot 2023-06-08 at 10 07 02

Can you think of why this might be happening?

@ocean90 ocean90 added the duplicate This issue or pull request already exists label Jun 15, 2023
@ocean90
Copy link
Member

ocean90 commented Jun 15, 2023

Hi there, this is an issue with how the GitHub checks API works. Checks are attached to commit SHAs and the annotations are added to latest workflow run for the commit being tested. This is nothing this action can fix.

Duplicate of #577, #401, #280, #97, #93.

@ocean90 ocean90 closed this as not planned Won't fix, can't repro, duplicate, stale Jun 15, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 26, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants