I'm in a similar situation, and any public package that I work on I have to manually point at my fork and add the original repo as an upstream. I haven't had much luck with any of the Pkg commands for things like this.
I got very excited since I currently only can do ~10% of what I need through GitHub Desktop, and have to do the rest through the command line. Unfortunately it looks like GitKracken doesn't have proxy support yet. On Monday, October 3, 2016 at 7:31:57 AM UTC-7, Chris Rackauckas wrote: > > Thanks for the suggestion. For some reason I never checked to see if there > were other GUIs, but once you mentioned it I did quite a bit of Googling. I > am now using GitKraken and while it will take a bit to get used to, it's > already improving my productivity. Thanks for the suggestion. > > On Sunday, October 2, 2016 at 9:31:18 PM UTC-7, Tony Kelman wrote: >> >> The conclusion I'd take out of that is not to use GitHub Desktop. It >> tries to hide too many important things like this from you. As far as git >> GUIs go, try SourceTree, it has a much more direct mapping between command >> line operations and GUI buttons. > >
