[GRASS-dev] GitHub backport label proposal

[Even Rouault]

For the backport bot 
(https://github.com/OSGeo/gdal/blob/master/.github/workflows/backport.yml) 
to work, I believe the label must be exactly "backport {git_branch_name}"

Le 22/11/2022 à 18:47, Nicklas Larsson via grass-dev a écrit :
> I think this is a splendid idea!
>
> Would be good to keep the label as short as possible, perhaps:
> - "backport 8.0"
> - "backport 8.2”
> ?
>
> At any rate, I have no strong opinion regarding the form, I fully support the general idea.
>
> Best, Nicklas
>
>
>> On 22 Nov 2022, at 12:00, Markus Neteler <neteler at osgeo.org> wrote:
>>
>> Hi devs,
>>
>> Our generic "backport" label seems to be mildly confusing (backport to
>> which branch?).
>>
>> My suggestion is to adopt the approach of GDAL:
>>
>> - backport release 7.8
>> - backport release 8.2
>> ...
>>
>> Like this also multiple labels could be set.
>>
>> Opinions?
>>
>> cheers,
>> Markus
>>
>> -- 
>> Markus Neteler, PhD
>> https://www.mundialis.de - free data with free software
>> https://grass.osgeo.org
>> https://courses.neteler.org/blog
>> _______________________________________________
>> grass-dev mailing list
>> grass-dev at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/grass-dev
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev

-- 
http://www.spatialys.com
My software is free, but my time generally not.