Skip to content

linter pre-submits don't actually fail #283

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

Closed
ianlewis opened this issue Jun 13, 2022 · 3 comments · Fixed by #333
Closed

linter pre-submits don't actually fail #283

ianlewis opened this issue Jun 13, 2022 · 3 comments · Fixed by #333
Assignees
Labels
area:tooling An issue with project tooling and config type:bug Something isn't working

Comments

@ianlewis
Copy link
Member

The reviewdog presubmits don't actually fail even though they're set to fail on error.

Seems it's an issues with the Github actions that's been around a while? reviewdog/reviewdog#907

@ianlewis ianlewis added the area:tooling An issue with project tooling and config label Jun 13, 2022
@ianlewis
Copy link
Member Author

yeah... The exit code of reviewdog isn't used in the action.
https://github.com/reviewdog/action-yamllint/blob/master/entrypoint.sh

@ianlewis
Copy link
Member Author

@ianlewis ianlewis self-assigned this Jun 14, 2022
@ianlewis ianlewis added the type:bug Something isn't working label Jun 14, 2022
@ianlewis
Copy link
Member Author

It seems like the individual actions are fine, but the reviewdog binary itself doesn't return the right exit code in the case where it doesn't write to the Github API even though there are errors. This seems to be the issue folks are encountering here: reviewdog/reviewdog#907

Without making the changes to reviewdog I think we can just run the linters ourselves manually since we just want the exit code and don't need the PR comment reporting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:tooling An issue with project tooling and config type:bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant