[wix-devs] Issue #4753
r.sean.hall at gmail.com
Thu Jan 21 18:31:32 PST 2021
> Are the hard-coded paths in enlist.cmd somehow misleading, or am I
Yes, enlist.cmd is flawed today since it clones the repos from wixtoolset
instead of your fork. This would take some work since it would need to know
your username, and would need to know to create the fork if you haven't
forked it yet.
I recommend you rename your remote from 'origin' to 'upstream' (
https://docs.github.com/en/github/using-git/renaming-a-remote). Then add a
new remote named 'origin' to point to your fork (
On Thu, Jan 21, 2021 at 8:22 PM Ron Martin via wix-devs <
wix-devs at lists.wixtoolset.org> wrote:
> The repo you have cited leaves me confused on a git configuration issue:
> The flow given is:
> 1. Fork (github.com/wixtoolset/Home -> github.com/my-account/Home)
> 2. Clone (github.com/my-account/Home -> \\D:Repos\wixtoolset\Home)
> and likewise for "Core".
> This scenario doesn't appear to be compatible with running enlist Core
> from my D:\Repos\wixtoolset\Home folder.
> Won't enlist clone github.com/wixtoolset/Core, rather than
> Previously, I cloned directly from github.com/wixtoolset/Whatever.
> Are the hard-coded paths in enlist.com somehow misleading, or am I
> missing something?
> On 1/21/2021 4:41 PM, Sean Hall via wix-devs wrote:
> > If you're asking for how to do a pull request on GitHub, I think this
> > explains it -
> WiX Toolset Developer Mailing List provided by FireGiant
More information about the wix-devs