On 11/27, Cédric Krier wrote: > I did not succeed to find those cases but anyway I think we could try to > manage them by having GitHub creating the issue automaticaly by sending > an email to [email protected] at the creation of a new pull > request (with the patch attached will be a plus).
This is a great idea and I hope it works well for us. > I don't have access to > the configuration of this account but I guess it is possible to get this > configuration. I added you as one of the owners of the tryton account on github. Can you confirm you recieved the invitation ? you should now be able to invite other core committers if you need to. > In such case, we have 2 workflow options: > > - the patch is trivial then it can be applied by a committer directly > > - the patch needs rework and so we request the original author to > upload it on codereview.tryton.org > And if he doesn't, we still have the information to fix the issue > ourself. > > For me, the important thing is not to have the contributor to contribute > but to not lost the information he brought in the PL. > > @sharoon, is it a possible configuration? There is a github user account named tryton-ci which we had setup to try and configure continous integration on tryton repositories. I added the issue tracker email to the user, but it need verification before it can start receiving email alerts for pull requests sent. I really hope this works. Cheers Sharoon Thomas
