You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "Riepl, Gregor (SWISS TXT)" <Gr...@swisstxt.ch> on 2019/04/02 13:03:06 UTC
Re: [DISCUSS] WIP PRs and contribution transparency
> In order to be more transparent, I would like to propose that we put
> something like ' [WIP DO NOT MERGE]' in the PR title as my colleagues
> and I have done on some new PRs you can follow. Labels cannot be used
> as not every contributor is a committer. Once the PR is ready for
> merging, we can remove it.
Is it possible to attach bots to PRs, like for Issues?
That way, a bot could take care of attaching and removing labels, and
access control could be done according to the contributor's role.
Re: [DISCUSS] WIP PRs and contribution transparency
Posted by Rohit Yadav <ro...@shapeblue.com>.
Hi Gregor, currently we don't have access to any bot service as those accesses are restricted to only committers of the repositories now. Maybe one of us can explore the possibility of using our GitHub account to do it, but that's a good to have feature.
Regards,
Rohit Yadav
Software Architect, ShapeBlue
https://www.shapeblue.com
________________________________
From: Riepl, Gregor (SWISS TXT) <Gr...@swisstxt.ch>
Sent: Tuesday, April 2, 2019 6:33:06 PM
To: dev@cloudstack.apache.org
Subject: Re: [DISCUSS] WIP PRs and contribution transparency
> In order to be more transparent, I would like to propose that we put
> something like ' [WIP DO NOT MERGE]' in the PR title as my colleagues
> and I have done on some new PRs you can follow. Labels cannot be used
> as not every contributor is a committer. Once the PR is ready for
> merging, we can remove it.
Is it possible to attach bots to PRs, like for Issues?
That way, a bot could take care of attaching and removing labels, and
access control could be done according to the contributor's role.
rohit.yadav@shapeblue.com
www.shapeblue.com
Amadeus House, Floral Street, London WC2E 9DPUK
@shapeblue