Hi, I am relatively new to golang coming from a C++/Python world.
When contributing to C++/Python projects on GitHub, I usually fork the project, make changes to hit and submit a pull request to the author/maintainer. I found that the above didn't work for me. I am hoping to contribute to the following project https://github.com/scipipe/scipipe I am trying to ascertain if my challenges is because Golang has specific ways for contribution or the above project is setup differently. I can't tell as I am new to Golang. I clone the forked project to $HOME/go/src/github/scipipe and testing it in another directory. I found that whenever I run my small test program, it pulls from some archive rather than my cloned repository and hence is not able to see the changes I made. Is there some special way to import the module so that it picked my clone directory rather than pulling down a zip archive versioned copy ? ``` package main import ( // Import the SciPipe package, aliased to 'sp' sp "github.com/scipipe/scipipe" ) func main() { // Init workflow with a name, and max concurrent tasks wf := sp.NewWorkflow("hello_world", 4) // Initialize processes and set output file paths hello := wf.NewProc("hello", "echo 'Hello ' > {o:out}") world := wf.NewProc("world", "echo $(cat {i:in}) World >> {o:out}") // Connect network world.In("in").From(hello.Out("out")) wf.Nicholas() // Failed to find this new exported function I added } ``` Cheers -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/d312ffe3-24b5-4aad-a3e1-4e50a35e318an%40googlegroups.com.
