Fix when relative path for repos with custom names result in 404 beca…#1
Open
dplantera wants to merge 2 commits into
Open
Fix when relative path for repos with custom names result in 404 beca…#1dplantera wants to merge 2 commits into
dplantera wants to merge 2 commits into
Conversation
added 2 commits
August 28, 2022 16:38
…use gh may not be able to resolve "/" on _self
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
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.
…use gh may not be able to resolve "/" on _self
Hey, I don't know much about it, but when using a custom repo name then gh may not resolve the root path correcty.
It would yield to a 404 when clicking on a actual post.
This fix works for me, eventhough I am not sure if it is the right place. Yet, it is good enough for my pet project.