Implement weekly run for fetching sponsors and contributors#313
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ❌ Deployment failed View logs |
papermc-website | f38dd2b | Jun 23 2026, 06:47 PM |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces a new automated workflow for updating sponsor and contributor data, centralizes data fetching, and refactors how this data is retrieved and typed in the codebase. The main improvements are the addition of a scheduled GitHub Actions workflow to update data, the creation of a script to fetch and store sponsor/contributor information, and updates to the frontend code to consume this data from static JSON files rather than directly from APIs.
Automated Data Update Workflow
.github/workflows/update-data.yml) that runs weekly or manually to update sponsor and contributor data. It checks out thedatabranch, runs a data generation script, and commits any changes.Data Generation Script
scripts/update-data.ts) that fetches sponsors from OpenCollective and GitHub Sponsors, as well as contributors from the PaperMC repository, and writes this data to JSON files for use by the website.data:updatescript topackage.jsonto run the data update script manually.Frontend Data Fetching Refactor
src/utils/github.ts) to fetch contributor data from the static JSON file in thedatabranch, instead of paginating through the GitHub API at runtime.src/utils/sponsors.ts) to fetch sponsor data from the static JSON file, and refactored types to usetypealiases instead ofinterfacefor consistency with the new data source. [1] [2]