-
-
Notifications
You must be signed in to change notification settings - Fork 210
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
Clarify data breach risk with OAuth #2326
Merged
Merged
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
dngray
changed the title
Clarify data breach risk with OAuth (#2207)
Clarify data breach risk with OAuth
Nov 12, 2023
dngray
added a commit
that referenced
this pull request
Nov 12, 2023
Signed-off-by: Daniel Gray <[email protected]>
dngray
force-pushed
the
pr-clarify-oauth
branch
from
November 12, 2023 11:27
1616329
to
811f19f
Compare
✅ Deploy Preview for privacyguides ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for privacyguides ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
I made some changes to incorporate information from #2207 (comment) too, if you could take a look. |
LGTM i like those changes |
jonaharagon
approved these changes
Nov 13, 2023
freddy-m
approved these changes
Nov 13, 2023
dngray
added a commit
that referenced
this pull request
Nov 13, 2023
Signed-off-by: Daniel Gray <[email protected]> Jonah Aragon <[email protected]>
dngray
force-pushed
the
pr-clarify-oauth
branch
from
November 13, 2023 15:20
886261b
to
4d87144
Compare
dngray
added a commit
that referenced
this pull request
Nov 13, 2023
Signed-off-by: Jonah Aragon <[email protected]> Signed-off-by: Freddy <[email protected]>
dngray
force-pushed
the
pr-clarify-oauth
branch
from
November 13, 2023 15:32
4d87144
to
e845192
Compare
Signed-off-by: Jonah Aragon <[email protected]> Signed-off-by: Freddy <[email protected]>
dngray
force-pushed
the
pr-clarify-oauth
branch
from
November 13, 2023 15:33
e845192
to
f8570a4
Compare
This pull request has been mentioned on Privacy Guides. There might be relevant details there: |
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.
Changes proposed in this PR:
Closes: #2207