Markus, Please go ahead with new labels for backport, let’s start with “backport [branch name]”. If it becomes too noisy, it is easy to change (ie. the label names).
Best, Nicklas > On 22 Nov 2022, at 21:40, Even Rouault <even.roua...@spatialys.com> wrote: > > > Le 22/11/2022 à 19:51, Nicklas Larsson a écrit : >> Looks like a clever little bot. In case that is the way the community choose >> to go then the label will have to be “backport releasebranch_8_2”, which is >> very long… >> I also wonder how useful it would be at the moment for GRASS, e.g. wide >> ranging indentation changes often causes conflicts between main and latest >> release branches. > > Sure the bot just tries to git cherry-pick commits, and if they don't apply > cleanly, it obviously fails, with reports like > https://github.com/qgis/QGIS/pull/50943#issuecomment-1322647971 > > > -- > http://www.spatialys.com > My software is free, but my time generally not. > _______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
