Update templates to make mitigations faster and enable external users to report more easily #2137
Conversation
This file contains 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
|
Generated file outputs: legacyfingerprinting.json (45 more)
latestv4/android-config.json (13 more)
|
|
Generated file outputs: legacyfingerprinting.json (45 more)
latestv4/android-config.json (13 more)
|
SlayterDev
reviewed
Jun 12, 2024
|
Generated file outputs: legacyfingerprinting.json (45 more)
latestv4/android-config.json (13 more)
|
This was referenced Jun 13, 2024
Closed
Closed
This was referenced Jun 13, 2024
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Asana Task/Github Issue:
https://app.asana.com/0/1201870266890790/1207370685063605/f
Description
As discussed, we're removing the "create an issue" step from our regular mitigation flow to make it a bit more efficient. To that end I updated the PR template to explicitly prompt for the information we want the PR description to contain and adapted the issue template to be more user-friendly for potential non-internal folks reporting (should that ever occur 😉).
Reference