What problem does it solve?
Keeping sponsor listings consistent across multiple files is error-prone: the markuplint project displays GitHub Sponsors in four separate locations (two READMEs and two website pages), and manual updates often miss one file or misapply tier rules.
Core Features & Use Cases
- Active Sponsor Fetching: Queries the GitHub GraphQL API via
gh api graphql to retrieve current active sponsors, their avatars, and tier pricing.
- Tier-Based Listing Rules: Applies tier incentives correctly — Corporate ($100/mo) and Personal ($10/mo) sponsors get README/website listings, while $5/mo Badge sponsors are excluded.
- Synchronized Multi-File Updates: Updates all 4 listing files in sync, handles new sponsors, moves ended sponsors to Past sponsors, and reflects tier changes.
- Use Case: Run a periodic check to detect that a sponsor downgraded from $10 to $5, then remove their avatar from the README and website while keeping listings consistent everywhere.
Quick Start
Check the current active GitHub Sponsors for the markuplint organization and update all four listing files to match.