Feedback wanted: GitHub License Key & Sponsorships

[jlord]

We'd love to hear what GitHub-generated license keys for your sponsors might enable for you.

• What workarounds (if any) do you currently use for this? (e.g., GitHub oAuth)?
• What can you imagine using a sponsorship license key for?
• How do you envision this working with a sponsoring organization with multiple members?
• What questions or concerns does this bring up?
• What other feedback do you have?

[skade]

Hi Jessica,

A license key being attached to a sponsorship is a clear indicator a sale. GH Sponsors does not give us the information needed to properly send invoices with VAT to people if we attached services to the sponsorship. I have raised this problem to GH again and again, to no avail. If this is implemented in the current state of GitHub Sponsors, this becomes a tax hazard to the sponsored party.

I could be incorrect, in which case GH sponsors should provide documentation for sponsored parties around the issue.

Greeting from Berlin,
Florian

[warrenbuckley]

Yes this would be very useful indeed.
Currently I have rolled my own for a VSCode extension to remove a sponsorware message that is an Azure Function that is used as a proxy API request using GraphQL to GitHub.

Hopefully this repo/example will help anyone else considering doing the same.
https://github.com/warrenbuckley/Is-Github-Sponsor

This was easy todo as VSCode had APIs to ask the user to authenticate their GitHub credentials.
If this was more generic and avoid me having to roll my own that would be fab.

[johnlindquist]

I would love ❤️ to use Sponsor licenses for https://www.scriptkit.com/

You can see the sponsor page I tossed together today here:
https://github.com/sponsors/johnlindquist/

It would be nice if the license was included in the "You're now sponsoring" e-mail and/or on the sponsor confirmation page:

Workarounds

I'm planning on using a webhook to "generate" a license (probably just the id of the sponsorship from the graphql API) to hook to an email service and send them their license. Once they save the id, I'll just check to see if that id exists to allow them to use those features.

I'm investigating how much data I can get from the webhook and storing simple data in a Cloudflare KV vs. querying the graphql API to attempt to find the sponsor id. Since the Sponsors API can't filter, I imagine I'd have to query all sponsorships every time.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐