Remove trailing slash to avoid double slashes #21
Conversation
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
I had my remote set to: `https://company.example/some-org/some-repo/` Which is valid, but caused the generated links to have double slashes, which GitLab didn't like, and showed an empty page instead of the file. Changing my remote to: `https://company.example/some-org/some-repo` fixed the issue, but I think it would be better if the plugin handled this case.
Contributor
Author
|
Converted to draft cause it doesn't seem to work well yet, will fix it later |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
I had my remote set to:
https://company.example/some-org/some-repo/Which is valid, but caused the generated links to have double slashes where my slash suffix is, which GitLab didn't like, and showed an empty page instead of the file.
Changing my remote to:
https://company.example/some-org/some-repofixed the issue, but I think it would be better if the plugin handled this case.