-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
link-to-file-in-file-history
breaks when branches contain slashes
#2692
Comments
@jack1142 working fine for me |
@yakov116 I'm able to reproduce it on clean browser (Firefox) with only Refined GitHub installed. FYI, this is an example invalid link that button redirects to: |
|
Doing good today. I cant figure out why |
@yakov116 hmm, it actually should show on the page I linked in the issue description (as in, it's actually useful to have it there), it just doesn't seem to work properly with any branch that has slashes, I've been able to reproduce this on history page of file on Not working example on Not working example on Working example on |
@jack1142 in such a case looks like were not taking out the branch name entirely so it does not work! See working link |
@fregante would |
Damn branches with slashes, GitHub should really escape them. I don’t know if your solution works, but the alternative is to get the branch name from another part of the page like we do in other features. |
link-to-file-in-file-history
links to 404link-to-file-in-file-history
breaks when branches contain slashes
Or you can also look for other places where the file path is more easily accessible in the DOM. In some feature we use the meta tags in the document head. |
Bug appears on this page: https://github.com/Cog-Creators/Red-DiscordBot/commits/V3/develop/docs/install_linux_mac.rst
Clicking any of "See object at this point in history" buttons redirects to 404 page.
The issue might be related to the slash in branch name, but I'm not entirely sure.
The text was updated successfully, but these errors were encountered: