Discord domain migrations#408
Closed
blastoise186 wants to merge 3 commits into
Closed
Conversation
This was referenced May 4, 2020
Contributor
|
This stuff is not mandatory until 7th October + gearbot 2.0 is under development, so making this minor change 5 months in advance seems excessive. You are welcome to open a new PR in late-September ish if Gearbot 2.0 is not done yet. |
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
2 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.
What does this PR add/fix/improve/...
Please give some general info about the PR
Discord has recently switched their primary domain from discordapp.com to just discord.com
This PR switches some of the references over. It only updates those which are known to be safe i.e. discordapp.com to discord.com
Migration
If any migration is required for already setup instances please provide instructions/requirements here
Not directly as a result of this PR per se. However, it should help other instances with their migrations when the time comes.
Dependencies
If this requires any other PRs to be merged and deployed in other GearBot repositories please link them here
None known at this time. gearbot/Dashboard#11 has a relation to this PR, but is not directly affected by it.