Implement GitHub Sponsors data fetching

[canerakdas]

Enter your suggestions in details:

We need to fetch and integrate GitHub Sponsors data to provide a complete view of project supporters

The most likely place for implementation is in the supporters data generator:
apps/site/next-data/generators/supportersData.mjs

[bjohansebas]

The options I see to achieve this are:

• Make fetching GitHub Sponsors optional and enable it only when the token is available. The required token does not need any special permissions.
• Create a weekly or daily workflow that updates a JSON file with the sponsors from GitHub Sponsors.

Note: even if we manage to connect GitHub Sponsors with OpenCollective, we won’t be able to see who the individual donors were, since it will appear as a single payment in OpenCollective. So these are the options we have, unless someone can think of another approach?

[avivkeller]

Make fetching GitHub Sponsors optional and enable it only when the token is available. The required token does not need any special permissions.

We can add a token belonging to @openjs-vercel, if needed.

[ovflowd]

Make fetching GitHub Sponsors optional and enable it only when the token is available. The required token does not need any special permissions.

We can add a token belonging to @openjs-vercel, if needed.

+1

[MattIPv4]

👀 Random thought as we get into implementing this, why do we have a WithSupporters component that does not act as a context provider, and does not even render children passed into it? I feel it should just be named SupportersList?

https://github.com/ghraw/nodejs/nodejs.org/4eb7eecda7add0229f3a09367b099b3b472b3100/apps/site/pages/en/about/partners.mdx

[ovflowd]

👀 Random thought as we get into implementing this, why do we have a WithSupporters component that does not act as a context provider, and does not even render children passed into it? I feel it should just be named SupportersList?

4eb7eec/apps/site/pages/en/about/partners.mdx (raw)

🤷