-
Notifications
You must be signed in to change notification settings - Fork 43
Implement proper Google provider using its first-class API #155
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
Implement proper Google provider using its first-class API #155
Conversation
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
|
@JasonTheAdams Can you please add #152 (comment) here? |
|
@JasonTheAdams 638a0ac addresses your feedback in #152 (comment). The same wording was already present in several other places, so I updated it everywhere. |
|
@JasonTheAdams Can you please give this a re-review so we can get it merged? No changes compared to #152, other than the extra commit above. |
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.
This is great! LGTM! 🚀
I did push my typing refactor, so let me know if you have any thoughts on that before we merge.
Fixes #106
Replaces #152 (which was accidentally using the protected
feature/*branch prefix)