Repository navigation
docs: document the three undocumented Slack case commands - #174
Merged
Merged
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
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.
/dispatch-update-case,/dispatch-escalate-caseand/dispatch-engage-userare registered by the Slack plugin but appeared in neither the user guide nor the administrator reference, so an operator setting up slash commands had no description to paste. Both pages now cover them.The existing anchor gate only checks that one page agrees with itself, so a command missing from every page reported ok.
check-command-links.mjsnow also diffs the documented commands against theslack_command_*defaults inconfig.py, which is the check that would have caught this.Closes #134