There is a pip package called git-pull-request. Also the ruby gem ghi should also provide it.<br>So a 'pip install git-pull-request' should allow 'git  pull-request' to work from the repo directory<br><br><br>Sent from ProtonMail mobile<br><br><br><br>-------- Original Message --------<br>On Nov 11, 2019, 10:13 AM, Marc Feeley < feeley@iro.umontreal.ca> wrote:<blockquote class="protonmail_quote"><br><p dir="ltr"><br>
&gt; On Nov 11, 2019, at 1:10 PM, Lassi Kortela &lt;<a href="mailto:lassi@lassi.io">lassi@lassi.io</a>&gt; wrote:<br>
&gt;<br>
&gt; Indeed, resisting the temptation to push commits directly to master is a winning move for multi-contributor repos :)<br>
&gt;<br>
&gt; GitHub PRs correspond 1:1 to Git branches, so if you do all your work in topic branches, it's almost effortless to make a PR for each branch. The branches can come from the main repo or any fork: equally easy.<br>
&gt;<br>
&gt; As a bonus, all popular CI services automatically run CI for each PR, so if you go via PR you're merging only tested code to master.<br>
&gt;<br>
&gt; IIRC GitHub has some branch protection system so you can block direct commits to master. The switch is somewhere in the repo's settings.</p>
<p dir="ltr">Yes I see all the advantages now. But bad habits are hard to get rid of&#8230; I still haven&#8217;t found a painless way to do the github pull-requests from the command-line.</p>
<p dir="ltr">Could you guys share the steps that work for you? Do you use &#8220;hub&#8221;?</p>
<p dir="ltr">Marc<br></p>
<p dir="ltr">_______________________________________________<br>
Gambit-list mailing list<br>
<a href="mailto:Gambit-list@iro.umontreal.ca">Gambit-list@iro.umontreal.ca</a><br>
<a href="https://mailman.iro.umontreal.ca/cgi-bin/mailman/listinfo/gambit-list">https://mailman.iro.umontreal.ca/cgi-bin/mailman/listinfo/gambit-list</a><br>
</p>
</div>