www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitry Blotsky (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-9811) Request for GitHub OAuth token for "repo:status" access to Apache repos
Date Thu, 25 Jun 2015 19:36:04 GMT

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

Dmitry Blotsky commented on INFRA-9811:
---------------------------------------

Wait, but then how does Travis write statuses to the Apache repos? There must be a key that
was generated for them. Travis only write access to the build status of a commit and cannot
write to any other data: be it commits, issues, or PRs. Could we have a key of the same type?


> Request for GitHub OAuth token for "repo:status" access to Apache repos
> -----------------------------------------------------------------------
>
>                 Key: INFRA-9811
>                 URL: https://issues.apache.org/jira/browse/INFRA-9811
>             Project: Infrastructure
>          Issue Type: Task
>            Reporter: Dmitry Blotsky
>            Assignee: Tony Stevenson
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> The Apache Cordova project would like to request for a GitHub OAuth token with "repo:status"
permissions to github.com/apache/ repos to be generated. It would enable Buildbot to update
commit correctness status on GitHub.
> The key could be placed alongside the "github.passwd" file in the master directory, inside
a file called "github.key", or inside of "private.py", similarly to githubSecret.



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

Mime
View raw message