funding: surface organization and maintainer sponsorships - #1
Draft
Tristan-Stoltz-ERC wants to merge 1 commit into
Draft
funding: surface organization and maintainer sponsorships#1Tristan-Stoltz-ERC wants to merge 1 commit into
Tristan-Stoltz-ERC wants to merge 1 commit into
Conversation
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.
Summary
The organization-wide
FUNDING.ymlalready points to Tristan's personal GitHub Sponsors profile and Ko-fi, while the public ERC site links to the Luminous Dynamics organization Sponsors page.This change makes the organization-wide repository Sponsor button expose both GitHub Sponsors destinations while preserving the existing Ko-fi route:
Luminous-Dynamics— organization-level supportTristan-Stoltz-ERC— maintainer-level supportluminousdynamicson Ko-fi — existing alternative routeGitHub supports one sponsored organization plus multiple sponsored developers in
FUNDING.yml, so this keeps the two existing funding paths consistent without forcing one to replace the other.Why
Reduce donation-link fragmentation and make sponsorship discoverable directly from public repositories that inherit the organization default.
Scope
Funding metadata only; no project code changes.