www-infrastructure-issues mailing list archives

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

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

Geoffrey Corey commented on INFRA-9988:

Right now, it looks like the API for closing PRs on gitHub has changed, so asfgi-admin isn't
closing PRs correctly.

To quote [~humbedooh] from earlier today: "Our immediate findings seem to show that nothing
is wrong on our end, but that GitHub might be experiencing some issues or have changed the
logic behind pull requests a bit.

We're looking into it, but we have no solution at the moment."

As for granting access: it is not possible at the time because the permissions are not granular
enough. As it stand currently, if you have enough access to close issues/PRs, you have write
access to the GitHub mirror.

I have gone ahead an manually closed the PR for now.

> 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
> 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