On Wednesday, June 4, 2014 2:45:25 PM UTC-4, David Einstein wrote: > > I have found it most convenient to make a branch on the code in .julia and > work from there, then everything will work as if it were the normal > package. The package in the .julia directory is just a clone of the > project on GitHub. This is probably morally wrong somehow, but it is > convenient. >
That's what I do, too. It's a little tricky to get the remotes working correctly, though. From my bash history when I did this for Winston (within the .julia/v0.3/Winston folder): git remote rename origin upstream git remote add origin [email protected]:mbauman/Winston.jl.git # the push URL for your fork on GitHub This way, you can push modified branches to your GitHub repo (git push origin branchname) and open pull requests from there. Pkg seems to be perfectly content with this arrangement, updating the packages (now from upstream) just like normal. You could use a different naming scheme, but I think this is a fairly common way to set up a forked repo from github.
