This needs to be updated for post-GOPATH modules.
On Monday, 14 June 2021 at 20:35:22 UTC+1 Sachin maurya wrote:
> I think this post might help
>
>
> https://penthaa.medium.com/contributing-to-open-source-go-projects-on-github-a-recipe-to-clone-forked-go-repos-4b52a1b36489
>
> On Wednesday,
I think this post might help
https://penthaa.medium.com/contributing-to-open-source-go-projects-on-github-a-recipe-to-clone-forked-go-repos-4b52a1b36489
On Wednesday, February 3, 2021 at 1:24:12 PM UTC-5 yue.ni...@gmail.com
wrote:
> Thank you for the different approaches.
>
> I have settled on
Thank you for the different approaches.
I have settled on the go.mod approach as proposed by Shulhan.
Cheers
On Wednesday, 3 February 2021 at 02:31:04 UTC-8 Adrian Ho wrote:
> On 3/2/21 2:21 pm, Volker Dobler wrote:
> > To create a Github PR: git push to your fork (add it as an additional
> >
On 3/2/21 2:21 pm, Volker Dobler wrote:
To create a Github PR: git push to your fork (add it as an additional
git remote) and create the PR. The "fork" is just a vehicle for a
Github PR and nothing you do work on (or try to build).
For a concrete example of what Volker's talking about, see the
You either have to use the "replace" directive in go.mod, or:
Do not work on the fork. Do your work on a plain _clone_ of the
repo (which works without "replace"ing dependencies).
To create a Github PR: git push to your fork (add it as an additional
git remote) and create the PR. The "fork" is
