The biggest question is – do we need PR notifications here. I would vote for no. Better let's keep discussions in one place.
And no, PRs don't get lost. They all are on GitHub. If a PR was lost, that is a bug in GitHub and needs to be addressed ASAP. When we moved to the new workflow, those with rights to merge PRs (implicitly) agreed to go over PR list on a (semi)regular basis and merge them if they are good. Have a nice day, Māris. piektd., 2019. g. 12. jūl., plkst. 17:10 — lietotājs Huidae Cho (<[email protected]>) rakstīja: > > Markus, > > I don't think that list has PR notifications. That's only for actual merges, > not everything, if I'm not wrong. > > Best, > Huidae > > > On Fri, Jul 12, 2019 at 9:58 AM Markus Neteler <[email protected]> wrote: >> >> Hi, >> >> On Fri, Jul 12, 2019 at 6:12 AM Huidae Cho <[email protected]> wrote: >> > >> > Markus, >> > >> > I think I have a workaround. In the worst case scenario, if GitHub doesn't >> > support notification forwarding, we could create a dummy GitHub account >> > just for notifications and set its email address to >> > [email protected]. >> >> Well, we do have this list: >> >> https://lists.osgeo.org/pipermail/grass-commit/ >> >> which contains everything from GitHub (I had set it up like this). >> >> But I would like to see _only_ the PRs also here and not clutter this >> list with the other GH emails. >> Not sure how to do that... >> >> Best >> Markus > > > > -- > Huidae Cho, Ph.D., GISP, PE (MD), CFM, M.ASCE > Open Source GIS Developer, GRASS GIS Development Team > _______________________________________________ > grass-dev mailing list > [email protected] > https://lists.osgeo.org/mailman/listinfo/grass-dev _______________________________________________ grass-dev mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/grass-dev
