You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the repo is tagged with a version v1.0 for example
when trying to get the specific version if fails and gets the latest commit instead
I figured its because there is no mod file in the root of the repo and the module system looks for it to match the tag of the repo.
any way to overcome this ? without moving the mod file to the root of the repo ? or separating the go code into its own repository ?
the Go project does not use its bug tracker for general discussion or asking questions about the language. The Github bug tracker is only used for tracking bugs and proposals going through the Proposal Process.
Please see the Questions wiki page; it has a list of good places for asking questions. Thanks!
usgin golang 1.14
we are generating multiplelibraries in multiple languages so the repo structure is
.gitignore
README.md
generate\csharp ...
generated\go\libname
generated\go\libname\go.mod
the go mod file is not on root looks like this
the repo is tagged with a version
v1.0
for examplewhen trying to get the specific version if fails and gets the latest commit instead
I figured its because there is no mod file in the root of the repo and the module system looks for it to match the tag of the repo.
any way to overcome this ? without moving the mod file to the root of the repo ? or separating the go code into its own repository ?
Stackoverflow link:https://stackoverflow.com/questions/62990985/storing-go-mod-file-not-in-the-root-of-the
The text was updated successfully, but these errors were encountered: