-
Notifications
You must be signed in to change notification settings - Fork 203
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
Fixes #3139 - Implement first stages of private reporting flow #3147
Conversation
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.
so I understand the logic of most of the code, and I understand the urgency.
- There is one question about anonymous reporting button
- I have the feeling, we try to modify too much of the initial code instead of relying on what already exists. Basically the PR could probably be simpler with a smaller footprint. See my suggestions. I may have missed something in the logic.
This first files a public issues, with some placeholder text, then uses its public URL to add to a private issue's metadata (which contains the original reporter's data).
We don't want to return any info here, let's be explicit.
They're not amazing, but it's something.
4f2bfa8
to
6b655ec
Compare
OK, @karlcow, ready for re-review. Thanks for the suggestions so far! |
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.
@miketaylr I have reviewed again. one thing to change.
This allows us to pass in arbitrary metadata keys and values to be "wrapped" as HTML comments for the issue body
6b655ec
to
fff9a49
Compare
OK, pushed a fix! |
@miketaylr Thanks for the code, the pasta 🍝 and everything. |
r? @karlcow
The next one to tackle is probably #3146.