Mailing-List: contact dev-help@groovy.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@groovy.incubator.apache.org
Received-SPF: softfail (nike.apache.org: transitioning domain of
 cedric.champeau@gmail.com does not designate 54.76.25.247 as permitted
 sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAJ2HCd9+6btPaKiF8yk1EDUQM7wsdx-dkghbksotbEQ58OD0AA@mail.gmail.com>
References: <553FEFB9.6090105@gmx.net>
	<CAJ2HCd9+6btPaKiF8yk1EDUQM7wsdx-dkghbksotbEQ58OD0AA@mail.gmail.com>
Date: Wed, 29 Apr 2015 06:50:00 +0200
Message-ID: 
 <CADQzvmnroufdCe_8JyYMggsuzbvwD8EiLBNG8=k=nOSb21T97A@mail.gmail.com>
Subject: Re: Write access to github mirror
From: =?UTF-8?Q?C=C3=A9dric_Champeau?= <cedric.champeau@gmail.com>
To: dev@groovy.incubator.apache.org
Content-Type: multipart/alternative; boundary=089e01493c6e33268d0514d5b612

--089e01493c6e33268d0514d5b612
Content-Type: text/plain; charset=UTF-8

Hi Pascal,

There's no such thing as write access to the mirror, even for closing PRs.
You have to submit a dummy commit with something recognized by GitHub as a
message to close a PR. For example "Closes #3". Since such dummy commits
pollute the history, my suggestion would be that before merging a PR, we do
an interactive rebase and reword the last commit to include this.

Hope this helps.

2015-04-28 23:11 GMT+02:00 Guillaume Laforge <glaforge@gmail.com>:

> Can one of our kind mentors check if Pascal is well setup? or if there's
> anything we need to do?
> Or do we have to bring that to INFRA's attention?
>
> Guillaume
>
> 2015-04-28 22:38 GMT+02:00 Pascal Schumacher <pascalschumacher@gmx.net>:
>
> > Hello everybody,
> >
> > it seems that I do not have write access to
> > https://github.com/apache/incubator-groovy
> >
> > This means I can not close pull requests e.g.:
> > https://github.com/apache/incubator-groovy/pull/6 using the github GUI.
> :(
> >
> > -Pascal
> >
> >
>
>
> --
> Guillaume Laforge
> Groovy Project Manager
> Product Ninja & Advocate at Restlet <http://restlet.com>
>
> Blog: http://glaforge.appspot.com/
> Social: @glaforge <http://twitter.com/glaforge> / Google+
> <https://plus.google.com/u/0/114130972232398734985/posts>
>

--089e01493c6e33268d0514d5b612--