-
-
Notifications
You must be signed in to change notification settings - Fork 53
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
Vale action output showing up under different workflow #73
Comments
Adding another case of this issue in cloudquery/cloudquery#4413 Vale is showing up failed on an unrelated PR Labeler action |
I am encountering the same issue. Vale's result do show up in a different action entirely. |
The old value `github-pr-check` was attaching the report to a different check. See errata-ai/vale-action#73
The old value `github-pr-check` was attaching the report to a different check. See errata-ai/vale-action#73
The old value `github-pr-check` was attaching the report to a different check. See errata-ai/vale-action#73
The old value `github-pr-check` was attaching the report to a different check. See errata-ai/vale-action#73
* Make `vale`, actually `reviewdog` fail on error * Set vale's reporter to github-pr-review The old value `github-pr-check` was attaching the report to a different check. See errata-ai/vale-action#73
* Make `vale`, actually `reviewdog` fail on error * Set vale's reporter to github-pr-review The old value `github-pr-check` was attaching the report to a different check. See errata-ai/vale-action#73
* Make `vale`, actually `reviewdog` fail on error * Set vale's reporter to github-pr-review The old value `github-pr-check` was attaching the report to a different check. See errata-ai/vale-action#73
Also happens to me (I had previously opened #57). |
Encountering a similar issue. Is there any hint on what might cause this, yet? |
Did some digging around, and this seems to be an issue with GitHub Actions and its API, and it's been around for a while now: https://github.com/orgs/community/discussions/24616 And feedback from more people on the reviewdog project: reviewdog/reviewdog#403 It doesn't seem like this will be fixed anytime soon, so I think it might be better to just close this issue for now. |
I'm trying to add the vale-action to the Stoplight docs repository (this PR), and for some reason the reviewdog output with the annotations for the vale-action is being added under another workflow we have in our repo for checking markdown links:
Any ideas on why that might be happening? I tried removing the
markdown-link-check
workflow to see what happens, and that makes the reviewdog vale report show up correctly under the vale action.The text was updated successfully, but these errors were encountered: