What I do know as "creating a PR" is (generic terminology, not git)
Open GitHub and fork Geany into myname. Create a branch on github myname. Fetch geany myname from github. Switch to branch and edit it. Commit it. Open github and create PR.
The details may vary a bit, for example a subsequent fork may be "ff only", but generally it should be something like that. Now we have:
1. geany master 2. myname master on gitgub 3. myname branch on github 4. myname master on the local machine 5. myname branch 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...
If I understood the protected branches correctly, the scheme will be:
1. geany master - protected, writable to leading devs only. 2. geany mybranch on github - writable to myname as creator. 3. geany mybranch on the local machine.
Simpler, real origin, and GitHub PR-s are be used because they are convenient, not required. Though seeing all branches may be a bit too much for the leading devs.
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.
--- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/764#issuecomment-159019989