-
Notifications
You must be signed in to change notification settings - Fork 1.8k
[prow/ci] attempt to use file-level comments for vale's 1:1 errors #104109
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
[prow/ci] attempt to use file-level comments for vale's 1:1 errors #104109
Conversation
|
🤖 Thu Dec 18 17:45:42 - Prow CI generated the docs preview: |
scripts/prow-vale-review.sh
Outdated
| --arg subject_type "file" \ | ||
| '{body: $body, commit_id: $commit_id, path: $path, subject_type: $subject_type}') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a bit much.
| --arg subject_type "file" \ | |
| '{body: $body, commit_id: $commit_id, path: $path, subject_type: $subject_type}') | |
| '{body: $body, commit_id: $commit_id, path: $path, subject_type: "file"}') |
jldohmann
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice catch, i saw your tests in the NEVERMERGE PR: lgtm but i can test in the morning too if necessary
|
@jldohmann I'll wait 'til the morning anyway, as if I see something else, I'll feel compelled to go after that, too. 🙃 |
f5fb3da to
ab5d1cd
Compare
|
@maxwelldb: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
@jldohmann I noticed 422 errors for our line 1 Vale errors--GitHub was rejecting comment assignment to any lines that were not part of diffs on the PR.
Example: #103787, which had this in its build artifacts:
This PR attempts to assign all line 1 errors to
"file"comments instead. There may be an occasional false positive for anything that truly belongs on line 1, but the comment will not be lost and should still be intelligible.Demo: #104108