Sponsor dialog treats scheme-less custom funding URLs as repository-relative links #213189
Replies: 2 comments 1 reply
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
|
Hi @antonreshetov, Nice write-up. Your diagnosis matches standard browser behavior. An Workaround (repo side): use absolute URLs in custom: ["https://paypal.me/antongithub"] Quoting the value is also safer in YAML, especially inside a flow sequence like Quick audit: if you maintain several repos (or an org-level For a proper fix: the expected behavior you describe (normalize scheme-less values to Hope that helps! |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Sponsors
Body
Scheme-less
customfunding URLs are used as relative links in the repository Sponsor dialog, sending visitors to github.com instead of the funding site.Minimal configuration
.github/FUNDING.ymlon the default branch:Steps and actual result
https://github.com/torsher-app/paypal.me/antongithubinstead of PayPal.The same symptom affects https://github.com/massCodeIO/massCode: PayPal resolves to
https://github.com/massCodeIO/paypal.me/antongithub. Its scheme-less Gumroad custom link is affected too.Public configurations:
Expected result
Open the external funding site, normalizing the scheme-less URL before rendering the link. If a scheme is now required, validation and documentation should consistently say so.
The current documentation includes
octocat.comwithout a scheme. In github/docs#35690, GitHub also clarified that scheme-less strings which become valid HTTP URLs when prefixed are accepted. That issue concerns format documentation/Packagist, rather than this navigation bug.Verification details
Checked on 2026-11-15 using public HTTP responses and shipped client code:
externalFundingLinks[0].urlaspaypal.me/antongithub.e.urldirectly tohref. Its filter checksnew URL(t.trim(), window.location.origin)but does not normalize the value passed tohref.These responses and URL resolution match the reported navigation. The date this behavior began is unknown; this report does not establish a regression.
A repository-side workaround is an absolute URL:
This resubmits #213186 through the required web template after the API-created discussion was automatically closed.
All reactions