Agreed -- we need visibility in dev efforts earlier rather than later. Saying the PR must be complete before submitting may be counter productive.
On Thu, Oct 25, 2018 at 8:33 PM Jeremy Mitchell <[email protected]> wrote: > Like Dave said, I often request WIP PR's especially when trying to work > thru requirements and/or design. > > On Thu, Oct 25, 2018 at 7:04 PM Dave Neuman <[email protected]> wrote: > > > We encourage WIP pull requests and a feature shouldn’t have to be > complete > > before you open one. With that being said, I am not sure that we have > any > > fine grained control over that bot. > > > > On Thu, Oct 25, 2018 at 17:06 Gray, Jonathan <[email protected]> > > wrote: > > > > > Today we use this plugin to achieve asfgit interaction: > > > https://github.com/jenkinsci/ghprb-plugin > > > > > > I don't believe what you want is expressible and instead should wait to > > > open your PR until you're done. > > > > > > Jonathan G > > > > > > On 10/25/18, 3:47 PM, "Moltzau, Matthew" <[email protected] > > > > > wrote: > > > > > > Is it possible to configure the asfgit bot to not automatically run > > > tests on every push? > > > Not sure if this is just me, but a lot of times I tend to push > > > multiple times before tests > > > really need to be run. Sometimes I do a quick fixup and push after > an > > > initial push, which > > > triggers two test jobs. Or I might forget about a second commit I > > need > > > to also push since I > > > have a ‘commit and push’ mentality. > > > Thoughts? +1/-1? > > > > > > > > > > > >
