Thanks Gwen, will update the wiki then.

On Wed, Jul 15, 2015 at 1:03 PM, Gwen Shapira <gshap...@cloudera.com> wrote:

> The script just runs a git push, it will be with your user (from git
> configuration), so you need privileges to push.
>
> On Wed, Jul 15, 2015 at 12:59 PM, Guozhang Wang <wangg...@gmail.com>
> wrote:
> > Another questions regarding the "kafka-merge-pr.py" script: once a
> > committer gives a LGTM on the PR, could the contributor use the script to
> > push to the git repo himself, or it must be executed by the committer? I
> > thought it is the former case but seems not. If not we need to make it
> > clear on the wiki.
> >
> > Guozhang
> >
> > On Tue, Jul 14, 2015 at 5:44 PM, Ismael Juma <ism...@juma.me.uk> wrote:
> >
> >> On Tue, Jul 14, 2015 at 6:15 PM, Jun Rao <j...@confluent.io> wrote:
> >>
> >> > I made a couple of changes to the new Jenkins job. Could you try
> again?
> >> >
> >>
> >> It's still not working, unfortunately. It may or may not be related to:
> >>
> >> https://blogs.apache.org/infra/entry/mirroring_to_github_issues
> >>
> >> For b, if we can't easily change the behavior of pull request bot, we
> can
> >> > also just flip back and forth btw "In Progress" and "Open".
> >> >
> >>
> >> It turns out that the ASF bot doesn't change the status at all. Spark is
> >> using a different mechanism to cause the status change (via a
> `sparkuser`).
> >> The JIRA ticket status will have to be changed manually for now. I have
> >> updated the instructions accordingly. I was told in the INFRA channel to
> >> file a JIRA ticket and they would see if auto transition listeners can
> be
> >> used to automate this (no guarantees though).
> >>
> >> Ismael
> >>
> >
> >
> >
> > --
> > -- Guozhang
>



-- 
-- Guozhang

Reply via email to