Enhancement: Custom Integrations

[JacobCoffee]

Summary

We can utilize the new linked roles feature to build custom integrations for third-party services including OpenCollective, GitHub, and others. This is useful to identify sponsors/backers.

• Create integrations for OpenCollective, GitHub (for sponsors AND other data) and Polar.sh (?)

Basic Example

Drawbacks and Impact

No response

Unresolved questions

• (Ref Enhancement: Gamify Contributions #6) I want to also pull GitHub non-sponsor data for things like the commit club, where do the following:
  • Find a users GitHub name
  • Connect it to the Discord name
  • (Guild-Specific Setting): For all the target owner (organization/user) repositories, get that GitHub users commit count across all repos (should be configurable), and then assign the user on Discord the corresponding commit club role. See Enhancement: Gamify Contributions #6 for more details, as this is basically that!

---

Note

We utilize Polar.sh to engage in regular as well as pledge-based > sponsorship.

Check out all issues funded or available for funding on our Polar.sh dashboard

• If you would like to see an issue prioritized, make a pledge towards it!
• We receive the pledge once the issue is completed & verified
• This, along with engagement in the community, helps us know which features are a priority to our users.

[JacobCoffee]

See: https://github.com/Rapptz/open-collective-discord-auth for part of how others do it

[JacobCoffee]

https://discord.com/developers/docs/tutorials/configuring-app-metadata-for-linked-roles

[JacobCoffee]

Also https://discord.com/developers/docs/resources/application-role-connection-metadata#update-application-role-connection-metadata-records

[JacobCoffee]

https://github.com/discord/linked-roles-sample

[JacobCoffee]

Would probably be outside of the byte repo