Regarding github CI

[Kirill A. Korinsky]

Folks,

As you may have noticed a few weeks ago, I opened a PR https://github.com/macports/macports-ports/pull/20092 <https://github.com/macports/macports-ports/pull/20092> in which I propose enabling the execution of port test as part of GitHub's CI.

I understand that not all ports currently have tests, but a lot of them does.

My goal here is to enhance the quality of tests for the ports, which will allow me to proceed with a bot that runs `port livecheck...` and detects when ports are updated. Subsequently, it will open a PR to update a port with the updated version and checksums, but only if such a port has tests.

Why? To automate the process of updating ports. We have a vast number of ports, and many of them can be updated quite easily. Enabling the execution of port tests on GitHub will ensure that such automatically generated PRs are of sufficient quality to be merged.

What's the ultimate goal? To keep MacPorts dynamically updated.

--
wbr, Kirill

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20230906/ab199d5d/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20230906/ab199d5d/attachment.sig>