So I want to make a simple typo fix a user pointed out. Does that mean I make an entire GitHub fork, make the change, then submit a pull request even if it’s just a 2 letter fix? (And delete the fork after it’s pulled?)
So when the next fix comes along I do the same - make a fork, do the fix, pull request, clean up fork?
Thanks for the hand-holding!
From what I understand…yep! I’m kind of a Git newbie so if there’s a better way I’m interested in finding out!
not a github expert here (not at all), but I guess forking once is OK, you just need to update your fork wrt. the baseline once in a while…
Sorry you’re bumping into this too, but glad to hear it’s not just me. 
That’s what I keep finding on the web, but it’s always followed by a bunch of CLI stuff that assumes you’ve got the fork downloaded.
I’m trying to figure out how I can (or why I can’t) use the GitHub web UI to update my fork (that I made from the GitHub web UI).
I found some (slightly painful) steps to do it in the web UI but I can’t seem to replicate them AND they reported cause “dirty commits” upstream - so I don’t want to make things harder for those handling pull requests.
Trying really hard not to go on an unproductive Git rant…
I think an alternative is to create a branch in duplicati/duplicati, but I’m guessing that’s something for which most contributors won’t have permissions.
The first time I forked duplicati to make some changes, I tried to keep my fork up to date. It’s kind of a pain.
Initial local git setup (after forking on github):
git clone https://github.com/drwtsn32x/duplicati.git
cd duplicati
git remote add upstream https://github.com/duplicati/duplicati.git
Then every now and then I would run these commands to sync changes from the “upstream” (official repo) down to my local git repo, then I’d push the changes up to my own github fork:
git fetch upstream
git pull upstream master
git push
I stopped doing this when I discovered that the above doesn’t sync branches, tags, or releases. I googled how to sync those but it looked like a total pain.
So now I just delete my fork/repo after my pull request is accepted. I make a new fork if I want to submit another change. This is cleaner and works well for me - I have only submitted a few pull requests.
Yep you can’t do it from the GitHub web UI. You have to create a local git repo on your PC and then do the commands I mentioned above. But it’s not perfect - as I noted above it doesn’t sync everything!
I think branches are only for alternate development tracks, like you want to work on a feature without disrupting main development. At some point you merge the branch back into the master.
And you can’t create a branch on the main duplicati repo unless you have write access to it. And if you DID have write access you could just push an update directly without ever creating a fork!
Sure, that’s the EASY way - I’m trying to do it the lazy+RIGHT way.
I’m fighting many years of SVN use here. 