This repository was archived by the owner on Oct 5, 2025. It is now read-only.
Fixed broken link in "Registering slash commands" - #1383
Closed
1yne wants to merge 2 commits into
Closed
Conversation
Fixes issue #1378
Jiralite
approved these changes
Feb 22, 2023
Co-authored-by: Jiralite <33201955+Jiralite@users.noreply.github.com>
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Please describe the changes this PR makes and why it should be merged:
Fixes issue #1378. The link used to redirect to
/slash-commandsbut since that route doesn't exist, it resulted in a 404 page. So, I have changed the link to the Creating Slash Commands page which specifies the correct file structure mentioned in the tip