2 ms·
Unfortunately it starts slightly in the wrong end. Step one assumes you already know where on github to point it for go.mod, then some 11 things to run before
by IcePic 3y ago
Unfortunately it starts slightly in the wrong end.
Step one assumes you already know where on github to point it for go.mod, then some 11 things to run before you make a github repo for it. By that time you might have gotten a better idea for the name or so.
Either it should have started with creating the GH repo and go from there, or "fix" so that it starts off as a un-versioned go project and then tell users how to github it afterwards.
I get that not all guides can cover all possible entries, but this one just struck me as missing both "I didn't know I wanted it on github from scratch, this was just my 2 minute golang test and now I figured it should be versioned" and "as it grew from color-ls-in-go to golang-filesystem-utility I figured this other name would be better"
- IcePic 3y agoand don't get me wrong, it's a very good guide on what and how to set up your projects and how a good default looks when you grow your project. I was just slightly put off by the simple start being written as if you spent lots of time on golang where each new project has a plan and a purpose, as opposed to someone dipping their toes into golang and want to skip making the simpler mistakes.