Now we have:

geany master

myname master on gitgub

myname mybranch on github

myname master on the local machine

myname mybranch on the local machine

I cannot help but think that a total of 5 Geany copies are a bit too much for a simple PR. And copies 2-5 are not really related to geany master - "origin master" means myname master. Huh...

First off, branches aren't copies, they are just a "pointer" to a particular last commit, so there's virtually no overhead in having a hundred branches.

So, yes GitHub would (probably, but maybe not, depending on how they manage forks) have a second copy of the geany repo under your account, but that's all. By using a "myname" remote on your local "geany" clone, you don't add any overhead (but a 3-lines entry in .git/config to describe your remote).

The procedure itself is not much shorter, but there's less room for errors, and syncing is simpler - actually nil, you always start from the current geany master.

Again, just add your own remote on a geany/geany clone. your master branch will naturally track geany/geany@master, yet you can push any custom branches you want by a mere git push myname mybranch. And as the origin remote (geany/geany) would be read-only, there would be no room for error either, you just couldn't do anything wrong on the real repo, and as master would track geany/geany@master, you couldn't even mess with your fork's master with an accidental git push on master.

Just clone geany/geany git clone https://github.com/geany/geany.git geany, and add your remote git remote add myname https://github.com/myname/geany.git, and enjoy a simple life.

—
Reply to this email directly or view it on GitHub.