You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a continuous problem in https://github.com/envoyproxy/envoy where people ignore all of the warnings about opening issues/PRs that could be potential security issues / zero-days.
What we want is some very trivial way to apply regex rules to the text in issues and PRs that can block them with a message before they are opened. This way, we could filter for things like "crash", "segfault,", things that look like hex addresses, etc. Obviously this is imperfect but it would cover 99% of cases.
Maintainers/admins would need a way to override this so issues could be opened after they are cleared, but it could be as simple as not applying the rules for maintainers/admins.
Thank you for your consideration.
The text was updated successfully, but these errors were encountered:
Thinking about it more, the other way of approaching this would be to have an option for all issues/PRs to go into a moderation queue. This would be a lot more work to implement I would guess and a lot more work for maintainers. But throwing it out there.
We have a continuous problem in https://github.com/envoyproxy/envoy where people ignore all of the warnings about opening issues/PRs that could be potential security issues / zero-days.
Still, people open issues.
What we want is some very trivial way to apply regex rules to the text in issues and PRs that can block them with a message before they are opened. This way, we could filter for things like "crash", "segfault,", things that look like hex addresses, etc. Obviously this is imperfect but it would cover 99% of cases.
Maintainers/admins would need a way to override this so issues could be opened after they are cleared, but it could be as simple as not applying the rules for maintainers/admins.
Thank you for your consideration.
The text was updated successfully, but these errors were encountered: