Repository navigation
Magefiles in their own nested Go module #464
Replies: 1 comment 3 replies
|
It's not a good idea to have two modules in the same repo. It causes a lot of problems with go in general. You can do it, but it's kind of a pain. This might be fixable, but I'm not 100% sure yet. Can you show me what kind of output mage produces in this case? |
Yes, I’m still weighting the pros and cons of this solution.
Here is a small test repo: https://github.com/yann-soubeyrand/nested-go-module-test. Running |
|
Yeah, I think this is because mage is actually running in the root directory, so it's using the go.mod of the root directory. It probably shouldn't do that if you have a I think this is fixable, but I'm a little worried it may break other people. I'll have to look at it and do some testing. |
Yeah, I think this is because mage is actually running in the root directory, so it's using the go.mod of the root directory. It probably shouldn't do that if you have a
magefilesdirectory, instead it should change the current working directory to that directory to build the magefiles.I think this is fixable, but I'm a little worried it may break other people. I'll have to look at it and do some testing.