develooper Front page | perl.perl5.porters | Postings from April 2016

Re: github contributor notices

Thread Previous | Thread Next
From:
Ivan Pozdeev via perl5-porters
Date:
April 10, 2016 20:11
Subject:
Re: github contributor notices
Message ID:
570AB357.1030009@mail.mipt.ru
Googling around showed a way to disable Github's issue tracker for a 
project, citing an official Github support reply apparently
http://www.getsymphony.com/discuss/thread/34945/
(appears to have been done already)

For disabling pull requests, the best way appears to auto-close them 
with a bot:
http://stackoverflow.com/questions/27957454/preventing-pull-request-in-github
http://nopullrequests.com/ <-set up specifically as a workaround

It may be best to also explicitly state in the repo description that any 
issues must be filed with other means.

Finally, if the only thing the github mirror does is hold a copy of 
http://perl5.git.perl.org/perl.git ,
the question rises why it is needed at all.

On 10.04.2016 22:45, Kent Fredric wrote:
> On 11 April 2016 at 07:13, Craig A. Berry <craig.a.berry@gmail.com> wrote:
>> The pull-request-emailer cited above turns a PR into a patch series;
>> does that mean one e-mail per commit?  If so, sending those to RT is
>> going to create a
>
> Also, there's the whole "somebody rebased a pull request and repushed"
> that you have to find a way to "synchronise" if you go down that road.
>
> Given github themselves have a very poor grasp on that in general, I
> think this road of exploration is better described as "trouble and
> suffering"
>

-- 
Regards,
Ivan


Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About