www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Rosen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-9988) Spark GitHub PRs didn't get closed automatically after merge
Date Tue, 14 Jul 2015 18:55:06 GMT

    [ https://issues.apache.org/jira/browse/INFRA-9988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626857#comment-14626857
] 

Josh Rosen commented on INFRA-9988:
-----------------------------------

One way to work around GitHub's lack of permission granularity might be to set up an ASF-managed
service which connects to GitHub with admin credentials and exposes a subset of the admin's
permissions to project committers over a REST API.  For instance, I think it would be possible
to build a service to allow committers to request PRs to be closed by clicking on a bookmarklet
which sends a request to an ASF-hosted service that handles that request on the committer's
behalf.

> Spark GitHub PRs didn't get closed automatically after merge
> ------------------------------------------------------------
>
>                 Key: INFRA-9988
>                 URL: https://issues.apache.org/jira/browse/INFRA-9988
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Git
>            Reporter: Xiangrui Meng
>            Assignee: Geoffrey Corey
>
> Many recent PR remained open after merge, for example, https://github.com/apache/spark/pull/7367.
This might be related to INFRA-9782. Since this issue happens from time to time, it would
be nice to grant Spark PMCs (or committers) access to close PRs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message