www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Nalley (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:58:05 GMT

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

David Nalley commented on INFRA-9988:

Yes, and we actually have a piece of code that does that, but hasn't yet been deployed. 
We're currently focused on finding out what has changed with our existing setup, and assuming
we don't get timely entry into the early access program for improved org perms, we'll start
considering deploying that code as a service. 

> 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

View raw message