New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: use server relative URL #10406
docs: use server relative URL #10406
Conversation
Are you sure that will work properly once deployed? It seems broken from the GitHub PR file preview "rich diff"? Current "server relative link" from GitHub "rich diff" preview:
Working link to file on
|
🤔 Not 💯 sure, but it seems a GitHub UI bug. Those links work when used in issues. |
e0ab4c4
to
ca847ff
Compare
It works for me too when I tried it in a issue preview screen. 😉 |
ca847ff
to
096099a
Compare
This is ready for a final review now, sorry for the mess/noise I caused with my force pushing, I wanted to clean up the final commit message. 🙈 |
Co-authored-by: Michael Kriese <michael.kriese@visualon.de>
🎉 This PR is included in version 25.41.1 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Changes:
Context:
Steps to reproduce the current problem:
I think it makes more sense to use a server relative link, as people will click on the link online more often than they will use the link locally on a cloned repository.
Documentation (please check one with an [x])
How I've tested my work (please tick one)
I have verified these changes via: