{{ message }}
Repository navigation
docs: automatically display current sponsors in README - #5748
Merged
Merged
Conversation
Contributor
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.

Summary
Display active, public GitHub sponsors as an avatar wall below Special Sponsor in the README. Every avatar links to https://github.com/sponsors/marktext; when no current public sponsors remain, the heading and wall are removed.
A daily and manually triggered GitHub Actions workflow fetches all sponsorship pages and commits README changes only when needed. API failures preserve the existing content. Special Sponsor stays independently maintained. No setup document is included.
Type of change
Test plan
Notes for reviewers
No related issue was supplied. No additional dependencies are needed. Live synchronization requires the repository SPONSORS_TOKEN secret after merge into develop (the default branch). The workflow uses SPONSORS_PUSH_TOKEN for checkout/push when configured, falling back to GITHUB_TOKEN. For protected develop, provide a repository-scoped token belonging to an identity allowed to push and bypass the PR requirement. SPONSORS_TOKEN is independently used to read sponsorships.
By submitting this pull request, I confirm that my contribution is made under the terms of the MIT license.