That's actually very good idea, because processor only comments when there is an issue and these are generic recommendation.
Greg, do you want to write down some nice proposal for such a template? LZ On Thu, Aug 31, 2017 at 10:32 AM, Timo Goebel <[email protected]> wrote: > ... do you just want to print some general hints for users for every new PR? > Or actively check that and automatically complain on every push? > I think prprocessor is already too chatty for my taste. > Maybe a Github PR Template could help as an alternative? > > Timo > >> On 31. Aug 2017, at 10:22, Lukas Zapletal <[email protected]> wrote: >> >> Hey, >> >> I would like to propose a change of our PR processor to better handle >> some things which we see often: >> >> - empty description >> - splitting huge PRs into smaller ones >> - screenshots for UX changes >> >> Any ideas for other things we should point out? Comments? >> >> -- >> Later, >> Lukas @lzap Zapletal >> >> -- >> You received this message because you are subscribed to the Google Groups >> "foreman-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- Later, Lukas @lzap Zapletal -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
