That's really nice, I had no idea... It's well documented
<https://github.com/JuliaLang/julia/blob/58c04e2ac5806919254c39996696029a897f407d/doc/manual/packages.rst#code-changes>,
too.
On Wednesday, October 21, 2015 at 7:36:00 PM UTC-4, Tim Holy wrote:
>
> I find this much easier:
>
> julia> cd(Pkg.dir("BustedPkg"))
>
> # The next is optional, but recommended
> julia> ;git checkout -b myinitials/myfixedbranch
>
> julia> edit("src/BustedPkg.jl")
>
> julia> ;git commit -a -m "Fix broken stuff"
>
> julia> Pkg.submit("BustedPkg")
>
>
> The last line is probably the main thing you were missing.
>
> --Tim
>
> On Wednesday, October 21, 2015 04:09:06 PM Sheehan Olver wrote:
> > This is probably more of a git question, but thought I'd ask here
> anyways.
> > Right now if I want to make a fix for someone else's package (e.g., 0.4
> > deprecated warnings) my workflow is fairly complicated:
> >
> > 1) Create fork on github.com
> > 2) Delete .julia/v0.4/Foo
> > 3) git clone https://github.com/dlfivefifty/Foo.jl
> > 4) Edit code
> > 5) git commit/git push
> > 6) Create pull request on github.com
> > 7) Wait several days for pull request to be merged
> > 8) Delete .julia/v0.4/Foo
> > 9) Get updated main fork via Pkg.add("Foo"); Pkg.checkout("Foo")
> >
> >
> > Any way I can simplify this? It ends up being a lot easier to do the
> > following
> >
> > 1) File a git issue on Foo.jl's github page
> > 2) Pkg.update() when the issue is closed.
>
>
