You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Rajani Karuturi (JIRA)" <ji...@apache.org> on 2015/08/24 06:45:46 UTC
[jira] [Commented] (INFRA-10134) github integration for Pull/review
requests
[ https://issues.apache.org/jira/browse/INFRA-10134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14708771#comment-14708771 ]
Rajani Karuturi commented on INFRA-10134:
-----------------------------------------
Can I get an update please?
I think 1 & 2 are very important while 3 & 4 can be taken up later.
> github integration for Pull/review requests
> -------------------------------------------
>
> Key: INFRA-10134
> URL: https://issues.apache.org/jira/browse/INFRA-10134
> Project: Infrastructure
> Issue Type: Bug
> Reporter: Rajani Karuturi
>
> We(cloudstack) replaced review board with github PRs for the review requests due to the ease of use and familiarity. But, since github/apache/cloudsatck is a readonly clone, we are limited in functionality.
> Here are a list of things which would make using github PRs even more effective.
> 1. ability to force close a PR with no activity (right now the only way to close a PR with no activity from the author is to make a dummy commit with 'This close #xxx' message
> 2. marking the PR as discarded(probably by using labels) to differentiate accepted vs. rejected PRs.
> 3. ability to add assignee(s) to a PR
> 4. information on who merged the PR (it says asfgit merged the pr)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)