New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After moving Master to new server instance, "Repository/View on GitHub" fails #7690
Comments
Thanks for the report @danpoleary. I was able to reproduce this as well. To workaround this you can remove the repository from GitHub Desktop and then add it back, which should then point to the correct URL. |
Just tried that, now cannot get any enterprise repository. Keeps
trying old server path and cannot get to new enterprise path.
…On Wed, Jun 5, 2019, 9:33 AM Steve Ward, ***@***.***> wrote:
Thanks for the report @danpoleary <https://github.com/danpoleary>. I was
able to reproduce this as well. To workaround this you can remove the
repository from GitHub Desktop and then add it back, which should then
point to the correct URL.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#7690?email_source=notifications&email_token=AABTCDVW2Q3AE2IJQR2R3CTPY66DFA5CNFSM4HTXWHKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODW7WYFA#issuecomment-499084308>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABTCDT2QRBCPJWVMQYPOZ3PY66DFANCNFSM4HTXWHKA>
.
|
I did some more investigation on the issue. When I remove the repository, and add it back in by adding local, it shows up in 'other' instead of 'enterprise' and no longer allows me to view on GitHub. It is grayed out. I removed it again, renamed the folder on drive, and tried to reclone from server. It tried the old server. I then signed out of my enterprise, and resigned in to the new URL. This allowed me to clone a new copy, but again, it does not show up under 'enterprise' and option to view on GitHub is grayed out. |
It has gotten worse. Now that I added it back, I can no longer switch branches. Nor can I fetch origin. Removing and re-adding the repository has really messed up everything. |
@danpoleary I'm not sure how your repository would have gotten into that state just from removing it from the application and adding it back. Are you seeing any error messages when performing operations? It would be helpful if you could upload the log file so that I could take a closer look at what might be happening here. To access the log files go to the file menu in GitHub Desktop and select The log files are created daily -- please upload a log file as an attachment from a day where you experienced the issue. |
My log only contains:
Cannot click on "Fetch" in the UI. "View on GitHub" is greyed out. and the repository in question shows up under "Other" and not "Enterprise" No error messages are displayed. Dan |
We have validated that once we moved our repositories from server A to server B, and repoint the local to the new servers, GitHub desktop stops working on those repositories without any error messages in the log or on screen. I have checked this on Windows 10, Windows 7, Server 2012R2 and Server 2016. All Git GUI, Git bash, Eclipse, VS, etc... commands work. This only affects Desktop. |
@steveward If I completely de-install GitHub Desktop and remove the "appdata\roaming\GitHub Desktop" directory, then reinstall and re-add repositories, then everything works as expected. I have left one machine in the wonky state to help in finding the root cause of this issue. Let me know if you need anything from me. Dan |
Reported in #16319. |
Description
When a repository is moved from one server URL to another, and we re-point to the new server, everything works except when you click on "Repository/View on GitHub". It tries to open the old location, and not the new location.
All other commands/menus work (Fetch, Commit, Push. Pull, etc..)
Version
Steps to Reproduce
Expected Behavior
Browser opens repository at correct URL
Actual Behavior
Tries to open repository at old URL location
Additional Information
Logs
The text was updated successfully, but these errors were encountered: