We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We may require email verification prior to submission of reports.
I think we should consider this. I imagine that we could use the current form, such that:
We could make this change in a follow up, but this way we could keep the reporting mechanism from being hit by bots (accidental or not).
The text was updated successfully, but these errors were encountered:
I was mostly thinking that this might be easy to do because we already have a consent flow.
We could also just use the consent flow to verify the email for the current session, and store the verified email in the session.
Then the report form will have two options:
Sorry, something went wrong.
No branches or pull requests
We may require email verification prior to submission of reports.
I think we should consider this. I imagine that we could use the current form, such that:
We could make this change in a follow up, but this way we could keep the reporting mechanism from being hit by bots (accidental or not).
The text was updated successfully, but these errors were encountered: