Repository navigation
Add PR template + use forms for issues + update security policy - #716
Merged
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
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.
Let's see if this helps any? This is continuation of #705, as I'm trying to figure out how to (not) deal with other people's LLMs.
From now on, an issue is required for new non-maintainer PRs. This is mostly to keep track of bug reports that are filed as LLM-written PRs, which are then closed due to violating the contributing guidelines.
The issue templates now mandate using a form, rather than just a template in the edit field.
I've also relaxed the stated expectations for security policy response time to account for the volume of LLM-written reports.