Fix relative redirect for old socketslack location
#179
Conversation
This file contains 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
pkosiec
force-pushed
the
fix-redirect
branch
from
524087f
to
6119244
Compare
pkosiec
force-pushed
the
fix-redirect
branch
from
6119244
to
5d4e3e8
Compare
mszostok
approved these changes
Nov 25, 2022
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.
Description
Changes proposed in this pull request:
socketslacklocationUnfortunately the redirect worked only without trailing
/.Also, this page could be visible for users, so I changed the content to be more user-friendly.
This PR fixes these issues.
Preview
Try both URLs
https://fix-redirect.botkube-docs-dcb.pages.dev/next/installation/socketslack/
https://fix-redirect.botkube-docs-dcb.pages.dev/next/installation/socketslack
Related issue(s)
#178