lint error→warning; continue on - #154
Open
God-damnit-all wants to merge 1 commit into
Open
Conversation
God-damnit-all
force-pushed
the
patch-2
branch
from
September 6, 2026 00:12
5c3b551 to
71de776
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Every workflow run has been failing because of the linting errors. It would be useful to see if it builds afterward.
In keeping with the rest of the file, it's a one-liner. The redirection is so that the output can escape into stdout. If an error occurs, it prepends
::warning::to the error lines that have been joined with%0A(which GitHub Actions will translate to newlines) as a warning annotation.Wrapping the whole command in parentheses was necessary to avoid a yaml syntax error, since apparently it doesn't like it when you start with an open curly brace.
I've tested this out already and it works.