This might just work on it's own, since the old repo shares the same git history, but it will probably be confusing if we ever have to debug the code on the DO droplet for whatever reason, since the repository that's cloned there currently is from the old repo (https://github.com/awseale/discordBot) and will maintain that as the old .
@awseale or @DanceParty we'll probably want to update the repository's remote URI on the droplet via git remote set-url origin git@github.com:NYTDiscordBot/DiscordBot.git and then refresh the history with a git pull.
This might just work on it's own, since the old repo shares the same git history, but it will probably be confusing if we ever have to debug the code on the DO droplet for whatever reason, since the repository that's cloned there currently is from the old repo (https://github.com/awseale/discordBot) and will maintain that as the old .
@awseale or @DanceParty we'll probably want to update the repository's remote URI on the droplet via
git remote set-url origin git@github.com:NYTDiscordBot/DiscordBot.git
and then refresh the history with agit pull
.