Moral of the story: - EITHER create a new package called

Question

Moral of the story: - EITHER create a new package called

a different thing and don't ever ever ever mistakenly call a package a wrong name in the future
- OR nuke your Golang installation and/or your entire machine and start everything over like you never installed the language CLI

basically??

0

27.03.2022

2 ответов

14 просмотров

Bryan Joshua Pedini Автор вопроса

Pedro Aguiar
If I remember correctly, GitHub says changing your...

IK, tho there are a few things to take into consideration here... 1st - it's not GitHub, yeah the same "don't change your username" principle applies, but the actual gitserver username was already b.pedini, I didn't change it midway, it was already that, I just forgot it was that (on my GitHub I'm still bryanpedini tho when I did set up my personal git server I went with a shorter version of myself) 2nd - like I said, the username was already b.pedini in the git server, so the only thing I changed, is the package path in the go.mod file after realizing my mistake still thinking about GitHub when I only pushed the package on my personal git server instead 3rd - even if, I rebased the entire git history, I removed every reference to the old name, sudo removed the entire pkg folder from the GOPATH, I pushed the new history with *just* the new name on the git server and nuked the offline history so that downloading it back it didn't have any old dangling git commit or reference with the old name, even tho go should not care about git/svn/etc, so it should not look into the .git folder of the local repository, I think (and hope so 😡)

0

27.03.2022

Pedro Aguiar · Accepted Answer

Pedro Aguiar

If I remember correctly, GitHub says changing your username might have irreversible consequences. I believe it applies to Git as a whole

0

27.03.2022

Похожие чаты

Moral of the story: - EITHER create a new package called

2 ответов

Похожие вопросы