0

I have a GIT online repository for a Visual Studio Solution, but the IT people here completely reorganized the network and I lost my local repository. My sourcecode has some changes that aren't yet pushed, so I don't want to lose those. However, all attempts to connect my source to the repository have failed.

I am the only developer on the project, so I'm not worried on other people's code, just getting mine checked in.

Any help would be appreciated. I'm happy to give whatever additional information is needed.

ESDictor
  • 745
  • 2
  • 9
  • 22
  • On what server does the remote repo live? One on your company's network, or on the Internet? What happens when you try to pull or push? – CodeCaster Sep 20 '19 at 21:06
  • Update the remote URL with the one you get to clone the repository (are you using Azure Devops?) – Philippe Sep 20 '19 at 21:48
  • So you have everything local but just can't connect to remote to push your changes? You just need to update remote URL in that case. – Ppp Sep 20 '19 at 21:56
  • @CodeCaster Internet on GitHub. I'm not the repository owner, but I am a user. – ESDictor Sep 23 '19 at 17:05
  • @Philippe I'm not using Azure Devops. I can't seem to connect to the remote but I think it's just me not understanding. – ESDictor Sep 23 '19 at 17:06
  • @Ppp Using the Team Exporer in Visual Studio, how would I accomplish that? – ESDictor Sep 23 '19 at 17:07
  • You can edit the remote from Team Explorer -> Settings -> Repository Settings – Ppp Sep 23 '19 at 18:07
  • @Ppp I only see Global Settings, no Repository Settings in Team Explorer -> Settings – ESDictor Sep 23 '19 at 18:47
  • Interesting. I see it on mine! You could try setting remote url from command line. https://stackoverflow.com/a/2432799/4594986 – Ppp Sep 23 '19 at 19:19
  • @Ppp I tried another project and was able to set to the remote, but now I am getting the following error: "Error encountered while pushing branch to the remote repository: rejected Updates were rejected because the tip of your current branch is behind its remote counterpart. Integrate the remote changes before pushing again." – ESDictor Sep 23 '19 at 19:38
  • 1
    Hmm... I guess your remote has new commits that your local branch doesn't. Instead of doing a push you may wanna do a pull so you can merge remote into local. – Ppp Sep 23 '19 at 19:41

0 Answers0