infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Stein (JIRA)" <>
Subject [jira] [Commented] (INFRA-16869) Request for write access for bot account
Date Thu, 30 Aug 2018 01:21:00 GMT


Greg Stein commented on INFRA-16869:

Unfortunately, no ... this is at the core of the ASF (provenance matching to an ICLA), and
is fundamentally non-negotiable. Any possibility that a third-party could modify an ASF repository
(eg. sneak in a change to Prow after the PMC member performed their review) would lead to
"nope, can't do."

That said ... another approach would be for Infrastructure to review the bot code, be satisfied
that it will not modify the repository, and then host/operate the bot as a general service
for the Foundation. Could you provide a pointer to Prow, and your thoughts on how difficult
it might be to run as a service? (ie. low or high cost for Infra?)

> Request for write access for bot account
> ----------------------------------------
>                 Key: INFRA-16869
>                 URL:
>             Project: Infrastructure
>          Issue Type: Improvement
>          Components: Github
>            Reporter: Ahmet Altay
>            Priority: Major
> (Re-opening I serve as a PMC member
on Beam.)
> Hi, 
> I'd like to request my bot account on Github be given write access to the Beam github
> Bot account: 
> Beam repo: 
> I will be using this account to test a code review tool call Prow. It needs write access
to assign reviewers to PRs.
> > Having said that, we already have review tools for Beam - is the current option
not sufficient?
> [~humbedooh] are your referring to GitHub's builtin review tools? [~udim]udim is trying
to build a system to auto-assign relevant code reviewers and integrate it with GitHub's existing
tooling. Does it answer your question?

This message was sent by Atlassian JIRA

View raw message