docs: correct a CI comment that denied the JavaScript suite - #40
Merged
Conversation
A comment on the Java job said "There is no JavaScript test suite to run", forty lines above the web-ui-tests job that runs it. It was true when it was written and stopped being true when that suite landed. A reader taking the file at face value concludes the frontend is untested. The justification for skipping the frontend goals is unchanged and still correct — the cost, the npm registry, the risk of rewriting a tracked yarn.lock. Only the reason given for it being free was false, and it is replaced by the real one: the JavaScript suite has a job of its own. The header carried the same omission two lines from the top, describing one verdict where the workflow gives three. Correcting line 42 alone would have left the file half contradicting itself. Comments only. No step, no flag, no job changed; the diff contains no executable line. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This was referenced Sep 5, 2026
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.
A comment on the Java job said "There is no JavaScript test suite to run" — forty lines above the
web-ui-testsjob, in the same file, that runs it. It was true when written and stopped being true when that suite landed. A reader taking the file at face value concludes the frontend is untested.web-ui-testsrunsyarn testat line 67 of this fileThe justification for skipping the frontend goals is unchanged and still correct — the cost, the npm registry, the risk of rewriting a tracked
yarn.lock. Only the reason given for it being free was false, and it is replaced by the real one: the JavaScript suite has a job of its own.The header carried the same omission two lines from the top. Correcting line 42 alone would have left the file half contradicting itself.
Comments only. No step, no flag, no job changed — the diff contains no executable line. The YAML still parses and still declares
test(matrixubuntu-latest,windows-latest) andweb-ui-tests.The checks on this PR will pass, but they prove nothing here: only comments changed.
🤖 Generated with Claude Code