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
It appears that dagger init --sdk go overwrites an existing go.mod when run in a context directory with a go package. The context directory is usually the directory that has .git, but if no parent directory has one, it defaults to the directory where dagger.json is.
What is the issue?
Investigation after a report by @sagikazarmark in:
It appears that
dagger init --sdk go
overwrites an existinggo.mod
when run in a context directory with a go package. The context directory is usually the directory that has.git
, but if no parent directory has one, it defaults to the directory wheredagger.json
is.Also tested on v0.10.3 and got the same result.
Dagger version
dagger v0.11.1 (registry.dagger.io/engine) darwin/arm64
Steps to reproduce
From a directory that's not inside a git repo:
You'll see that there's no
go.mod
indagger/
and the rootgo.mod
has the SDK's dependencies now.Log output
The text was updated successfully, but these errors were encountered: