docs(README): added link to the github page doc - #347
Conversation
|
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please visit https://cla.developers.google.com/ to sign. Once you've signed (or fixed any issues), please reply here with What to do if you already signed the CLAIndividual signers
Corporate signers
ℹ️ Googlers: Go here for more info. |
|
Thanks! Please sign CLA and I can merge @FredaXin. This page also needs to be updated. |
|
@googlebot I signed it! and we'll verify it.
…On Sat, Feb 22, 2020 at 11:37 AM googlebot ***@***.***> wrote:
Thanks for your pull request. It looks like this may be your first
contribution to a Google open source project (if not, look below for help).
Before we can look at your pull request, you'll need to sign a Contributor
License Agreement (CLA).
📝 *Please visit https://cla.developers.google.com/
<https://cla.developers.google.com/> to sign.*
Once you've signed (or fixed any issues), please reply here with @googlebot
I signed it! and we'll verify it.
------------------------------
What to do if you already signed the CLA Individual signers
- It's possible we don't have your GitHub username or you're using a
different email address on your commit. Check your existing CLA data
<https://cla.developers.google.com/clas> and verify that your email is
set on your git commits
<https://help.github.com/articles/setting-your-email-in-git/>.
Corporate signers
- Your company has a Point of Contact who decides which employees are
authorized to participate. Ask your POC to be added to the group of
authorized contributors. If you don't know who your Point of Contact is,
direct the Google project maintainer to go/cla#troubleshoot (Public
version <https://opensource.google/docs/cla/#troubleshoot>).
- The email used to register you as an authorized contributor must be
the email used for the Git commit. Check your existing CLA data
<https://cla.developers.google.com/clas> and verify that your email is
set on your git commits
<https://help.github.com/articles/setting-your-email-in-git/>.
- The email used to register you as an authorized contributor must
also be attached to your GitHub account
<https://github.com/settings/emails>.
ℹ️ *Googlers: Go here
<https://goto.google.com/prinfo/https%3A%2F%2Fgithub.com%2Fgooglemaps%2Fgoogle-maps-services-python%2Fpull%2F347>
for more info*.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#347?email_source=notifications&email_token=ALSBYBK5OG3B5IXHL7ZCSF3REFIDJA5CNFSM4KZSYLUKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMVEPQA#issuecomment-589973440>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALSBYBMRK3N33ZSJD7UI54DREFIDJANCNFSM4KZSYLUA>
.
|
|
Singed! Thank you, Chris!
…On Mon, Feb 24, 2020 at 12:25 PM Chris Arriola ***@***.***> wrote:
Thanks! Please sign CLA and I can merge @FredaXin
<https://github.com/FredaXin>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#347?email_source=notifications&email_token=ALSBYBMK3BD3D7UTFU2YNU3REP7HDA5CNFSM4KZSYLUKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMYYZPA#issuecomment-590449852>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALSBYBIBJKTE5IAQE3DD5TLREP7HDANCNFSM4KZSYLUA>
.
|
|
CLAs look good, thanks! ℹ️ Googlers: Go here for more info. |
|
Merged. Travis failures are unrelated. |
|
It should be noted that these docs are not being updated with the current build process. |
|
🎉 This PR is included in version 4.2.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Docs are hosted but not linked, which is hard for user to find. Added the link to the docs.