docs(validation): correct the annotation-cap explanation in where-to-see-results - #380
Merged
hdamker merged 1 commit intoJul 21, 2026
Merged
Conversation
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
3 participants
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.
What type of PR is this?
documentation
What this PR does / why we need it:
Corrects
documentation/validation/where-to-see-results.md's "Annotations have limits" section. The GitHub annotation cap (10 errors / 10 warnings / 10 notices per workflow step — an Actions problem-matcher limit) applies to every pull request, not only forks or very large ones; the previous wording implied it was fork- or size-specific. Names the mechanism explicitly and explains the resulting "annotations only show on the first file" symptom.Which issue(s) this PR fixes:
Fixes #350
Special notes for reviewers:
Doc-only change; no code or test impact.
Changelog input
Additional documentation
This section can be blank.