endpoints: add patreon endpoint #668

ghostdevv · 2023-09-15T22:02:28Z

Adds the patreon endpoints from their documentation.

https://docs.patreon.com/#oauth.

I've tested these thoroughly whilst making a pr to pocketbase.

google-cla · 2023-09-15T22:02:32Z

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

ghostdevv · 2023-09-15T22:04:47Z

Signed CLA

gopherbot · 2023-09-15T22:15:46Z

This PR (HEAD: a0c2ff5) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/oauth2/+/528640.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to register for Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2023-09-15T22:27:12Z

Message from Gopher Robot:

Patch Set 1:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/528640.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2023-09-15T22:27:13Z

Message from Gopher Robot:

Patch Set 1:

Congratulations on opening your first change. Thank you for your contribution!

Next steps:
A maintainer will review your change and provide feedback. See
https://go.dev/doc/contribute#review for more info and tips to get your
patch through code review.

Most changes in the Go project go through a few rounds of revision. This can be
surprising to people new to the project. The careful, iterative review process
is our way of helping mentor contributors and ensuring that their contributions
have a lasting impact.

Please don’t reply on this GitHub thread. Visit golang.org/cl/528640.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2023-09-22T11:42:48Z

Message from Matt Hickford:

Patch Set 1:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/528640.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2023-09-23T20:24:22Z

This PR (HEAD: d9d4120) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/oauth2/+/528640.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to register for Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2023-09-23T20:31:36Z

Message from GHOST Dev:

Patch Set 2:

(2 comments)

Please don’t reply on this GitHub thread. Visit golang.org/cl/528640.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2023-09-23T20:38:50Z

Message from Matt Hickford:

Patch Set 2: Code-Review+1 Run-TryBot+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/528640.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2023-09-23T20:45:57Z

Message from Gopher Robot:

Patch Set 2:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/528640.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2023-09-23T20:45:57Z

Message from Gopher Robot:

Patch Set 2: TryBot-Result+1

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/528640.
After addressing review feedback, remember to publish your drafts!

ghostdevv · 2024-01-17T17:56:24Z

Bump 🙏

gopherbot · 2025-02-02T21:11:10Z

This PR (HEAD: 7d68d33) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/oauth2/+/528640.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2025-02-02T21:19:08Z

Message from Jorropo:

Patch Set 2: Commit-Queue+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/528640.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-02-02T21:19:08Z

Message from Go LUCI:

Patch Set 2:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2025-02-02T21:05:08Z","revision":"b2c8ba7181408fe26a17a1654da0f9a4648d116c"}

Please don’t reply on this GitHub thread. Visit golang.org/cl/528640.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-02-02T21:19:09Z

Message from Jorropo:

Patch Set 2: -Commit-Queue

Please don’t reply on this GitHub thread. Visit golang.org/cl/528640.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-02-02T21:19:09Z

Message from Go LUCI:

Patch Set 2:

This CL has failed the run. Reason:

Tryjob golang/try/x_oauth2-gotip-linux-arm64-boringcrypto has failed with summary (view all results):

go on master (commit 37f27fb)
oauth2 on master (change 528640)

Build or test failure, click here for results.

To reproduce, try gomote repro 8724012551938661505.

Additional links for debugging:

Output for test golang.org/x/oauth2 module

Please don’t reply on this GitHub thread. Visit golang.org/cl/528640.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-02-02T21:19:10Z

Message from Go LUCI:

Patch Set 2: LUCI-TryBot-Result-1

Please don’t reply on this GitHub thread. Visit golang.org/cl/528640.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-02-02T21:19:10Z

Message from Jorropo:

Patch Set 3: Commit-Queue+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/528640.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-02-02T21:19:11Z

Message from Go LUCI:

Patch Set 3:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2025-02-02T21:11:48Z","revision":"a3cf4432cd320f5b38c3e04b1d1309785afe5005"}

Please don’t reply on this GitHub thread. Visit golang.org/cl/528640.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-02-02T21:19:11Z

Message from Jorropo:

Patch Set 3: Auto-Submit+1 Code-Review+2

Please don’t reply on this GitHub thread. Visit golang.org/cl/528640.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-02-02T21:27:06Z

Message from Jorropo:

Patch Set 3: -Auto-Submit

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/528640.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-02-02T21:27:06Z

Message from Jorropo:

Patch Set 3: -Commit-Queue

Please don’t reply on this GitHub thread. Visit golang.org/cl/528640.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-02-02T21:27:07Z

Message from Go LUCI:

Patch Set 3:

This CL has passed the run

Please don’t reply on this GitHub thread. Visit golang.org/cl/528640.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-02-02T21:27:07Z

Message from Go LUCI:

Patch Set 3: LUCI-TryBot-Result+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/528640.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-02-02T21:27:08Z

Message from Jorropo:

Patch Set 4: Auto-Submit+1 Code-Review+2 Commit-Queue+1

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/528640.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-02-02T21:34:56Z

Message from Go LUCI:

Patch Set 4:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2025-02-02T21:20:17Z","revision":"147665de6c822e27819b4b2a5e464c8d14dc037b"}

Please don’t reply on this GitHub thread. Visit golang.org/cl/528640.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-02-02T21:34:57Z

Message from Jorropo:

Patch Set 4: -Commit-Queue

Please don’t reply on this GitHub thread. Visit golang.org/cl/528640.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-02-02T21:34:57Z

Message from Go LUCI:

Patch Set 4:

This CL has passed the run

Please don’t reply on this GitHub thread. Visit golang.org/cl/528640.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-02-02T21:34:58Z

Message from Go LUCI:

Patch Set 4: LUCI-TryBot-Result+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/528640.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-02-03T17:44:57Z

Message from Cherry Mui:

Patch Set 4:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/528640.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-02-03T18:19:26Z

Message from Jorropo:

Patch Set 4: -Auto-Submit

Please don’t reply on this GitHub thread. Visit golang.org/cl/528640.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-02-03T18:28:35Z

This PR (HEAD: 890ef05) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/oauth2/+/528640.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2025-02-03T19:36:59Z

Message from GHOST Dev:

Patch Set 5:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/528640.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-02-03T19:37:00Z

Message from Jorropo:

Patch Set 5: Auto-Submit+1 Code-Review+2 Commit-Queue+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/528640.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-02-03T19:45:07Z

Message from Go LUCI:

Patch Set 5:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2025-02-03T19:29:36Z","revision":"0e34d0b9cec1d76d0523ee12fafc44a847370edf"}

Please don’t reply on this GitHub thread. Visit golang.org/cl/528640.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-02-03T19:45:08Z

Message from Cherry Mui:

Patch Set 5: Code-Review+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/528640.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-02-03T19:45:09Z

Message from Jorropo:

Patch Set 5: -Commit-Queue

Please don’t reply on this GitHub thread. Visit golang.org/cl/528640.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-02-03T19:45:09Z

Message from Go LUCI:

Patch Set 5:

This CL has passed the run

Please don’t reply on this GitHub thread. Visit golang.org/cl/528640.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-02-03T19:45:10Z

Message from Go LUCI:

Patch Set 5: LUCI-TryBot-Result+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/528640.
After addressing review feedback, remember to publish your drafts!

Adds the patreon endpoints from their documentation. https://docs.patreon.com/#oauth. I've tested these thoroughly whilst making a pr to pocketbase. pocketbase/pocketbase#3323. Change-Id: I023871a4340ee4ebcba9fd808d4a8f0c081fc10e GitHub-Last-Rev: 890ef05 GitHub-Pull-Request: #668 Reviewed-on: https://go-review.googlesource.com/c/oauth2/+/528640 Reviewed-by: Cherry Mui <[email protected]> Reviewed-by: Carlos Amedee <[email protected]> Reviewed-by: Jorropo <[email protected]> Auto-Submit: Jorropo <[email protected]> LUCI-TryBot-Result: Go LUCI <[email protected]>

gopherbot · 2025-02-06T22:59:22Z

This PR is being closed because golang.org/cl/528640 has been merged.

feat: add patreon

a0c2ff5

ghostdevv mentioned this pull request Sep 15, 2023

Add Patreon Auth pocketbase/pocketbase#3323

Closed

fix: switch to endpoints.go

d9d4120

ghostdevv changed the title ~~Add Patreon Endpoints~~ endpoints: add patreon endpoint Sep 23, 2023

Merge branch 'golang:master' into patreon

7d68d33

fix: reorder

890ef05

gopherbot closed this Feb 6, 2025

endpoints: add patreon endpoint #668

endpoints: add patreon endpoint #668

Conversation

ghostdevv commented Sep 15, 2023 • edited Loading

google-cla bot commented Sep 15, 2023

ghostdevv commented Sep 15, 2023

gopherbot commented Sep 15, 2023

gopherbot commented Sep 15, 2023

gopherbot commented Sep 15, 2023

gopherbot commented Sep 22, 2023

gopherbot commented Sep 23, 2023

gopherbot commented Sep 23, 2023

gopherbot commented Sep 23, 2023

gopherbot commented Sep 23, 2023

gopherbot commented Sep 23, 2023

ghostdevv commented Jan 17, 2024

gopherbot commented Feb 2, 2025

gopherbot commented Feb 2, 2025

gopherbot commented Feb 2, 2025

gopherbot commented Feb 2, 2025

gopherbot commented Feb 2, 2025

gopherbot commented Feb 2, 2025

gopherbot commented Feb 2, 2025

gopherbot commented Feb 2, 2025

gopherbot commented Feb 2, 2025

gopherbot commented Feb 2, 2025

gopherbot commented Feb 2, 2025

gopherbot commented Feb 2, 2025

gopherbot commented Feb 2, 2025

gopherbot commented Feb 2, 2025

gopherbot commented Feb 2, 2025

gopherbot commented Feb 2, 2025

gopherbot commented Feb 2, 2025

gopherbot commented Feb 2, 2025

gopherbot commented Feb 3, 2025

gopherbot commented Feb 3, 2025

gopherbot commented Feb 3, 2025

gopherbot commented Feb 3, 2025

gopherbot commented Feb 3, 2025

gopherbot commented Feb 3, 2025

gopherbot commented Feb 3, 2025

gopherbot commented Feb 3, 2025

gopherbot commented Feb 3, 2025

gopherbot commented Feb 3, 2025

gopherbot commented Feb 6, 2025

ghostdevv commented Sep 15, 2023 •

edited

Loading