Event JSON
{
"id": "b0dd3262d82f427bfbed9204d83514e0543eda784a5e3aedb51e68180ee87e2c",
"pubkey": "46f3c7bb33cc3019049b76dc89dbb96e34c247bdda68b6ad8632682793ff8a1a",
"created_at": 1790613173,
"kind": 9802,
"tags": [
[
"comment",
"Solution for it can be nostr/ngit "
],
[
"i",
"https://iain.rocks/blog/dont-couple-your-go-code-to-github"
],
[
"r",
"https://iain.rocks/blog/dont-couple-your-go-code-to-github",
"source"
],
[
"textquoteselector",
"-",
"in, and I’ll explain why.Problem",
"I’ve seen this problem become su"
],
[
"textpositionselector",
"705",
"1212"
],
[
"rangeselector",
"/main[1]/p[3]",
"/main[1]/p[3]",
"0",
"507"
]
],
"content": "The main problem with using your git hosting location is that your code is now coupled to a hosting provider. That is, if you move your git hosting to GitLab then you have to change your code! Otherwise, you’ll be fetching the old verison. This can result in you being unable to change git hosting provider because the amount of overhead in switching. So you literally end up with your code coupled to GitHub. Which sounds completely nuts, but it’s something that is pretty much defacto in the Go community.",
"sig": "7f7c6f1a6631c6ed89f67b964cc8cb912b4fb3f2dcf5fcb3d7358635bda2ac28ecfa4c94294e6856fdf22975bd68ae7a1b79df7c0850048ee2a4249b3ce6df2a"
}