<p>How would committing on the Geany repo itself simplify creating PRs?  Creating a GitHub fork is one click, once.  Then, just add this new remote to your existing Geany clone (the "official" one) (just once, again), and do just like you'd do if you only used that one, but push your feature/pr branches to your own remote.</p>

<p>For example, I'd do:</p>

<div class="highlight highlight-source-shell"><pre>(on master) $ git pull --ff--only <span class="pl-c"># get new changes, as usual</span>
(on master) $ git checkout -b my-pr-branch
(on my-pr-branch) $ <span class="pl-c"># do some editing as needed</span>
(on my-pr-branch) $ git commit -a -m <span class="pl-s"><span class="pl-pds">"</span>Fix something very important<span class="pl-pds">"</span></span>
(on my-pr-branch) $ git push b4n my-pr-branch <span class="pl-c"># publish my branch on my own fork</span></pre></div>

<p>I guess I totally miss the point, but I fail to see how specifying the remote in the <code>git push</code> call is a cumbersome.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br>Reply to this email directly or <a href="https://github.com/geany/geany/issues/764#issuecomment-158673021">view it on GitHub</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ABDrJ_T2c527EYue6STlP2jpQ39qTjSzks5pILkjgaJpZM4Glekm.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/geany/geany/issues/764#issuecomment-158673021"></link>
  <meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue on GitHub"></meta>
</div>