Hi,
I have a build task in a go module that refers to an upstream module in go.mod
How do I make sure the task rebuilds if the go code in the upstream task changes? Looks like I have to manually insert /upstream/**/*.go at the moment to the inputs for the downstream task. Can it be handled by the go toolchain?
The toolchain does insert the upstream project as a project dependency, but I'm not sure if there's a way to do group(^:sources) or equivalent to tell moon to check for the source code upstream as well
Ref:
|
pub fn extend_project_graph( |
Hi,
I have a
buildtask in a go module that refers to an upstream module ingo.modHow do I make sure the task rebuilds if the go code in the upstream task changes? Looks like I have to manually insert
/upstream/**/*.goat the moment to theinputsfor the downstream task. Can it be handled by the go toolchain?The toolchain does insert the
upstreamproject as a project dependency, but I'm not sure if there's a way to dogroup(^:sources)or equivalent to tell moon to check for the source code upstream as wellRef:
plugins/toolchains/go/src/tier2.rs
Line 16 in 3c2df06