-
Notifications
You must be signed in to change notification settings - Fork 141
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
update version check to check for upcoming repo rename
- Loading branch information
Showing
1 changed file
with
17 additions
and
15 deletions.
There are no files selected for viewing
This file contains 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
a23ea9c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So, when is the rename happening? Right now, the update check is failing due to missing repo. :)
a23ea9c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It currently should be doing two update checks, one against the current repo name and one against the old one. Unless I screwed that up...
a23ea9c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@wilg ah, that makes sense, and now I see it from reading the code. I just kept seeing version check failures because of the 404.
a23ea9c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool! I'm waiting a while to hopefully get people to upgrade to the version that includes this change before making the migration. I think GitHub may end up redirecting when I rename anyway, but better safe than sorry!