feat: introduce linter to run on PR builds #592
+167
−1
Conversation
This file contains 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
yankay
force-pushed
the
FixFromAsCasing
branch
2 times, most recently
from
1c8376e to
1507e62
Compare
Signed-off-by: Kay Yan <[email protected]>
yankay
force-pushed
the
FixFromAsCasing
branch
from
1507e62 to
cb857bb
Compare
|
Could you please assist in reviewing the pull request (PR)? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #350
📑 Description
To catch a variety of small, quick-to-happen mistakes, an additional action now runs a linter on the PR content.
✅ Checks
ℹ Additional Information