> On 3 Feb 2021, at 10.17, Nicholas Yue <yue.nicho...@gmail.com> wrote:
>
> 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 ?
>
Inside the go.mod file in your test directory, add the "replace" directive.
Something like this may works,
----
module mytestmodule
replace github.com/scipipe/scipipe => ../path/to/your/clone
----
More on Go modules,
* https://blog.golang.org/using-go-modules
* https://golang.org/ref/mod
--
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/D4B065B8-12C3-4DDF-8190-13A8D7EA0FAA%40gmail.com.
