Open
Conversation
PabloCorso
force-pushed
the
bn-store-to-db
branch
from
4d01f44 to
302afdd
Compare
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.
Battle Notifier migration discussion here.
Related PRs:
What changes are proposed in this pull request?
Add new section under
settings/notificationspage for Battle Notifier.The user must connect to Discord to use
!bnbot.Then, the user can set notification using the Discord bot.
The
!bncommand can be copied with a clickNote: Beyond this setup, the user experience with battle notifications remains the same. This is a first step towards making it possible to improve the UX for notifications from the website but it is not the purpose of these current changes.