For https://gitbox.apache.org/setup/ , after completing the first two steps, is there any action needed for "MFA Status" box ?
Cheers On Fri, Jul 7, 2017 at 1:37 PM, Lukasz Cwik <lc...@google.com.invalid> wrote: > for i in range(0, inf): +1 > > Note that the URL for gitbox linking is: > https://gitbox.apache.org/setup/ (above > URL was missing '/' and was giving 404) > > > On Fri, Jul 7, 2017 at 1:21 PM, Jason Kuster <jasonkus...@google.com. > invalid > > wrote: > > > Hi Beam Community, > > > > Early on in the project, we had a number of discussions about creating an > > automated tool for merging pull requests. I’m happy to announce that > we’ve > > developed such a tool and it is ready for experimental usage in Beam! > > > > The tool, MergeBot, works in conjunction with ASF’s existing GitBox tool, > > providing numerous benefits: > > * Automating the merge process -- instead of many manual steps with > > multiple Git remotes, merging is as simple as commenting a specific > command > > in GitHub. > > * Automatic verification of each pull request against the latest master > > code before merge. > > * Merge queue enforces an ordering of pull requests, which ensures that > > pull requests that have bad interactions don’t get merged at the same > time. > > * GitBox-enabled features such as reviewers, assignees, and labels. > > * Enabling enhanced use of tools like reviewable.io. > > > > If you are a committer, the first step is to link your Apache and GitHub > > accounts at http://gitbox.apache.org/setup. Once the accounts are > linked, > > you should have immediate access to new GitHub features like labels, > > assignees, etc., as well as the ability to merge pull requests by simply > > commenting “@asfgit merge” on the pull request. MergeBot will communicate > > its status back to you via the same mechanism used already by Jenkins. > > > > This functionally is currently enabled for the “beam-site” repository > only. > > In this phase, we’d like to gather feedback and improve the user > experience > > -- so please comment back early and often. Once we are happy with the > > experience, we’ll deploy it on the main Beam repository, and recommend it > > for wider adoption. > > > > I’d like to give a huge thank you to the Apache Infrastructure team, > > especially Daniel Pono Takamori, Daniel Gruno, and Chris Thistlethwaite > who > > were instrumental in bringing this project to fruition. Additionally, > this > > could not have happened without the extensive work Davor put in to keep > > things moving along. Thank you Davor. > > > > Looking forward to hearing your comments and feedback. Thanks. > > > > Jason > > > > -- > > ------- > > Jason Kuster > > Apache Beam / Google Cloud Dataflow > > >