Did GitHub change how open source contributors get sponsored?

Did GitHub change how open source contributors can get sponsored

GitHub still lets eligible open source contributors receive payments through GitHub Sponsors, but the workflow has changed. The program now highlights sponsored developers and organizations, adds repository sponsor buttons, and gives sponsors more ways to manage and scale support.

The part people get wrong is thinking GitHub removed sponsorship or turned it into a different product. GitHub’s current docs still describe the same core idea: if you contribute value to open source and live in a supported region, you can join GitHub Sponsors and receive sponsorships. The change is in the tooling and presentation, not in the basic purpose.

GitHub has also made the public face of sponsorship more visible. A repository can show a sponsor button through a FUNDING.yml file, and that button can point to GitHub Sponsors, external funding platforms, or custom funding URLs. That makes sponsorship easier to discover from the project page itself, which matters when donors are looking at a repo before they decide where to spend money.

The inconvenient part is that sponsorship still depends on setup and eligibility. GitHub says contributors must live in a supported region, and the profile flow still requires the standard sponsored-developer setup. If a contributor is outside a supported region, GitHub points them to a waitlist rather than opening access immediately.

GitHub has also changed what sponsors can do on the buyer side. The Sponsors dashboard now supports bulk sponsorships, dependency-based discovery, and org-level views of sponsorship activity. That is a real change for maintainers who depend on organization funding, because the sponsor experience is no longer just one person clicking a monthly amount on a profile.

Another change is that GitHub has added more explicit controls around sponsorship duration. Sponsors can set an end date, and GitHub documents that the final charge and the visible active period do not end on the same day. That detail matters for budgeting and for anyone reading the sponsorship status too quickly.

GitHub also keeps the platform tied to open source contribution, not only code. Its docs list bug reports, issue triage, documentation, leadership, business development, project management, mentorship, and design as valid contributions for sponsored-developer eligibility. That is broader than the narrow “write code, get paid” version people often assume.

The other thing people miss is that the sponsor button and the sponsorship profile are separate surfaces. A repository can advertise funding links even when the person or team behind it is not using every GitHub Sponsors feature the same way. In practice, that means a project can look sponsor-ready without every maintainer being set up identically.

If you are deciding whether a contributor can get sponsored now, the answer is yes, through GitHub Sponsors, if they meet GitHub’s current eligibility rules. If you are asking whether GitHub changed the system, the answer is also yes: it has expanded discovery, repository-level visibility, and sponsor management around the same core sponsorship model.

For teams that want a simple practical next step, the clean path is to set up the sponsor profile, add the repository funding file, and then check whether the project surface shows the button where donors actually look. If you want a separate place to coordinate testing or project work, DevConnect keeps that outside GitHub and is free to use at https://devconnectplatform.com, which can help when sponsorship and contribution are happening in different places.

FAQ

Did GitHub stop GitHub Sponsors? No. GitHub still documents GitHub Sponsors for receiving sponsorships and for sponsoring open source contributors. The product exists, and the current docs still describe how contributors and sponsors use it.

Can a repository show funding links without a GitHub Sponsors profile? Yes. GitHub’s funding file supports GitHub Sponsors, external funding platforms, and custom URLs, so a repo can point to more than one funding destination.

Can organizations sponsor maintainers now? Yes. GitHub’s documentation covers organization sponsorships, org dashboards, and bulk sponsorship activity. The platform is built for both individual and organization support.

Does sponsorship only count for code contributions? No. GitHub’s eligibility language includes non-code work such as issue triage, documentation, mentorship, leadership, business development, project management, and design.