www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (INFRA-7918) Provide Spark with a github access token that allows closing PR's
Date Wed, 18 Jun 2014 18:52:26 GMT

     [ https://issues.apache.org/jira/browse/INFRA-7918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gavin closed INFRA-7918.
------------------------

    Resolution: Fixed

So yeah you can already close PRs with your current commit messages, just add in there somewhere
'this closes #1234' .

TIAS

> Provide Spark with a github access token that allows closing PR's
> -----------------------------------------------------------------
>
>                 Key: INFRA-7918
>                 URL: https://issues.apache.org/jira/browse/INFRA-7918
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Git
>            Reporter: Patrick Wendell
>            Assignee: Gavin
>
> At present, we have no way for the committership to close pull requests on github. Since
sometimes users abandon requests, this has lead to an infinitely growing queue on our github
page.
> https://github.com/apache/spark/pulls
> As a short-term solution to this, would it be possible for infra to provide (via the
private list) the Spark committership with a temporary API token that has the permission to
close pull requests? Then we can write a small script that our committers can use to close
them. You can create tokens here:
> https://github.com/settings/tokens/new
> I think this is a decent temporary solution because:
> 1. This token could have very limited permissions. The only permission would be to close
pull requests. Closing requests doesn't do anything irreversible, the user can always open
them up again.
> 2. If there are any issues, infra can immediately revoke/delete the token.
> Let me know if you would consider this. I think it's a decent solution and right now
this is becoming a bigger issue for us.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message