>What I would really like is an up to date "learn how to handle Go project in 30 minutes"
1. git init
2. git remote add %something%
3. go mod init %name_of_your_module% (where in most common case name is your repo address without the https part)
4. https://github.com/golang-standards/project-layout - this repo has the default project structure. Each subfolder has README that describes the purpose of the folder
5. go get -u github.com/gin-gonic/gin to add gin (web lib) for your project. Same for any other package. The will be added to your go.mod and go.sum files
5.1 import "github.com/gin-gonic/gin" in your code to use gin
5.2 package may have more than one major version (tag). If you want to use package at latest tag 2 - you add '/v2' when you 'go get' the package (i.e. go get -u github.com/gin-gonic/gin/v2)
6. git commit && git push to publish
7. Not sure what to you mean by 'fork&clone&submit&pr including 3rd party submodules'. You may use vendoring but in most cases you don't need it as you have your dependencies in your go.mod && go.sum files. You may want to read more about vendoring and gomodproxy though.
8. Testing is pretty easy but I guess you want and article about best practices? I won't post any link as I find the topic as too controversial regardless of the language\stack
9. CI - not sure that does this have to do with the language
10. haven't done much profiling or debugging to fill you in.
1. git init
2. git remote add %something%
3. go mod init %name_of_your_module% (where in most common case name is your repo address without the https part)
4. https://github.com/golang-standards/project-layout - this repo has the default project structure. Each subfolder has README that describes the purpose of the folder
5. go get -u github.com/gin-gonic/gin to add gin (web lib) for your project. Same for any other package. The will be added to your go.mod and go.sum files
5.1 import "github.com/gin-gonic/gin" in your code to use gin
5.2 package may have more than one major version (tag). If you want to use package at latest tag 2 - you add '/v2' when you 'go get' the package (i.e. go get -u github.com/gin-gonic/gin/v2)
6. git commit && git push to publish
7. Not sure what to you mean by 'fork&clone&submit&pr including 3rd party submodules'. You may use vendoring but in most cases you don't need it as you have your dependencies in your go.mod && go.sum files. You may want to read more about vendoring and gomodproxy though.
8. Testing is pretty easy but I guess you want and article about best practices? I won't post any link as I find the topic as too controversial regardless of the language\stack
9. CI - not sure that does this have to do with the language
10. haven't done much profiling or debugging to fill you in.