I noticed something odd about the backport bot, it is not running actions
(QA  checks):

[Backport 2.21.x] [GEOS-10487] Log4J custom logging XML configuration is
case-insenstive <https://github.com/geoserver/geoserver/pull/5931>

> This branch has no conflicts with the base branch when rebasing
> Rebase and merge can be performed automatically.


Trying things out:
- Converting to draft, and then ready-for-review, does not trigger the QA
actions
- any other ideas?

--
Jody Garnett


On Mon, 6 Jun 2022 at 00:48, Andrea Aime <andrea.a...@geosolutionsgroup.com>
wrote:

> Hi all,
> during the weekend I've set up again the backport bot, based on QGIS own
> fork of it.
> It seems to be working, as usual:
>
>    - Open a PR, label it with the "backport <targetBranch>" label
>    - On PR merge, the bot will try to create a backport PR, and will
>    comment on the original PR if it cannot (e.g., conflict)
>
> The QGIS folks have one more customization on the token being used by the
> bot (I'm guessing customization of the rights the bot runs with), that our
> configuration currently does not have. I've inquired about it on
> qgis-devel, will update when I get an answer from them.
>
> Give it a try, if all works fine we can port the same configuration over
> to GeoTools and GeoWebCache as well.
>
> Cheers
> Andrea
>
> ==
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax:     +39 0584 1660272
>
> mob:   +39  333 8128928
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> -------------------------------------------------------
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
> _______________________________________________
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to