thanks I'm just starting to play with/understand the integration, and think we should start worrying about "what makes a good process here"
while I like the idea of a "press-to-merge" button, it's not going to do the whitespace stripping on a merge we ought to be doing and it gets signed by the github GPG key, rather than any private key which some but not enough of us use. Similarly: where do discussions go, how best to review, etc, etc. I've got no idea of best practises here. Some experience of the spark process, which has * A template for the PR text which is automatically used to initialize the text * strict use of reviewers demanding everything right (no committer-final-cleanup) * the ability of trusted people to ask jenkins to run tests etc 1. Any other ASF projects to look at? 2. who fancies trying to define a process here on a confluence page? On Mon, Mar 4, 2019 at 8:05 AM Akira Ajisaka <aajis...@gmail.com> wrote: > This issue was fixed by ASF infra team. > If there are any problems, please let me know. > > Regards, > Akira > > On Mon, Mar 4, 2019 at 3:25 PM Akira Ajisaka <aajis...@gmail.com> wrote: > > > > Hi folks, > > > > I found github and gitbox are inconsistent and filed > > https://issues.apache.org/jira/browse/INFRA-17947 to fix it. > > > > Regards, > > Akira > > --------------------------------------------------------------------- > To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org > For additional commands, e-mail: common-dev-h...@hadoop.apache.org > >
