I like #3 as well. If you're not already using some form of pull request creation script, I recommend the `hub <https://github.com/github/hub>` command from GitHub. I like submitted a pull request from the same terminal window where I'm performing all my other operations.
On Thu, Jul 11, 2019 at 8:23 AM Jesse Glick <[email protected]> wrote: > On Thu, Jul 11, 2019 at 7:51 AM Daniel Beck <[email protected]> wrote: > > 3. Start with PRs, but merge myself when maintainers don't. This is > basically what Oliver ended up doing when we added Jenkinsfiles to plugin > repositories.[2] > > +1 for this. An unmentioned benefit over #1 is that CI will catch > fatal mistakes in your tool, and if you are doing some batch POM > transformation with hundreds of cases you are going to have made a > couple of mistakes. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr34ErzvKcCVgWCP%2BoqMXTsOND4-OGH0Ddqup3YMSMvE%3DA%40mail.gmail.com > . > For more options, visit https://groups.google.com/d/optout. > -- Thanks! Mark Waite -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtEwz%3DeTCVsQ%3DEu611S_js%3Do3%3D6K%3D6g5URZdpJ0RVJ9kwg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
