-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(bug-report): ask for confirmation before opening issue #4543
Conversation
040652b
to
096ad65
Compare
096ad65
to
c1cc046
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have left some suggestions but no blockers
Co-authored-by: Thomas O'Donnell <andytom@users.noreply.github.com>
Well, I will keep using my local patch that removes this subcommand.
At least the confirmation should expect an uppercase You can avoid a little bit more complexity by saving the (long) report to a temporary file and link to the bug tracker. |
…#4543) * feat(bug-report): ask for confirmation before opening issue * Apply suggestions from code review Co-authored-by: Thomas O'Donnell <andytom@users.noreply.github.com> Co-authored-by: Thomas O'Donnell <andytom@users.noreply.github.com>
Description
Privacy concerns have been voiced about the privacy tool (#3757). To avoid any data from being exposed unintentionally, ask for confirmation before forwarding issue reports to GitHub.
Unlike #3794, this PR avoids complexity by simply asking for confirmation instead of allowing edits of generated reports.
Motivation and Context
Closes #3757
Closes #3794
Screenshots (if appropriate):
How Has This Been Tested?
Checklist: