Note annotation limits in Problem Matchers documentation #734
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
This was referenced Mar 12, 2021
konradpabjan
approved these changes
Mar 29, 2021
There was a problem hiding this comment.
These changes look good to me 👍 Thanks for putting out this PR @electronjoe!
Here is some corresponding info that some of our support staff have documented: https://github.saobby.my.eu.orgmunity/t/maximum-number-of-annotations-that-can-be-created-using-github-actions-logging-commands/16991/2
@thboop @ericsciple Just FYI as code owners
Fixup text Co-authored-by: Konrad Pabjan <konradpabjan@github.com>
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.
A number of developers have worked hard to get GH Action Problem Matchers working for a new class of Annotations - to find that they are not displayed on the PR of interest due to restrictions on Annotation counts in GH Actions.
This PR proposes documenting the limitation and making the limitation visible up-front (and hints at some solutions - though better / more complete examples would be welcome).