Repository navigation
feat: add org-wide FUNDING.yml for GitHub Sponsors - #10
Merged
Merged
Conversation
Now that GitHub Sponsors is enabled for the org, adds a Sponsor button to every repo that doesn't already have its own FUNDING.yml, pointing at the org's Sponsors listing rather than any individual.
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
1 participant
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.
GitHub Sponsors is now enabled for the org (
sponsors-drumandbyteslisting, public). This adds the org-defaultFUNDING.yml, which gives every repo without its own funding config a "Sponsor" button pointing at the org listing.Updates the README table + drops the now-stale "FUNDING.yml is intentionally not included yet" line.