Add guidelines for bulk reporting of issues - #1905
Open
StanFromIreland wants to merge 1 commit into
Open
Conversation
Documentation build overview
|
Member
|
I'm not sure if we should be encouraging any form of bulk reporting, even via single issues. It's still a lot of work for us to churn through, bulk findings are likely found via tools and not from actual real-life use, and we probably don't really need to fix them all? I agree @devdanzin has been finding useful stuff, although he got in touch first to ask how (or whether) to report. But I think this is an exception rather than something to encourage as policy. |
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
2 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.
This came up recently when a user opened a large number of issues (>45) in an hour, as the result of LLM analysis. This wasn't ideal, and we asked them to report as a single issue, in the same style @devdanzin has been doing (and has been working well for us). As such, I propose we document this so that we can link to it if this happens again.