5

So today we renamed a repo on bitbucket. We changed the remote url on local PCs and kept working. When deploying, our deploying platform threw an error saying invalid repo name, which was expected. Thing is, said platform doesn't have a "change repo remote url" option, so we did it manually over SSH. It didn't work as it now says the bitbucket token is invalid. There is no option to change or set the token. Redeploying will take almost an entire day due to configurations. FML.

Comments
  • 0
    One trick I use with SVN is doing a new "checkout" of the repo branche while the folder already contains the files. It will notice and just do a file check and corrects all the links etc. without redownloading the files.

    Maybe it will work on your GIT repo aswell? Try to remove the repo link and set it again and do a "pull"?!
Add Comment