Error reporting if bot added with wrong scope #170
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
Zabuzard
requested review from
I-Al-Istannen,
Tais993,
d3vel0per,
illuminator3 and
marko-radosavljevic
|
Kudos, SonarCloud Quality Gate passed! |
I-Al-Istannen
approved these changes
Oct 8, 2021
Tais993
approved these changes
Oct 8, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
If the bot is added to a guild, but with wrong permissions (for example: missing the slash commands scope), it will now report the problem to the guild and also log a warning.
Port from the stale #119 which did not survive the massive refactoring introduced in
develop.