I have a couple of suggestions to improve our GitHub workflows that could reduce unnecessary resource usage without sacrificing coverage.
Junichi has built a robust PHP unit test suite and Tomáš made sure the tests pass on both Windows and Linux. Since the tests are extensive, the PHP editor tests take ~1.5hrs. This has been brought up in previous threads. The PHP tests are run in the PHP and Windows workflows. I propose following to reduce wasting GitHub Actions resource: 1. Use the "on: [push,pull-request]: paths:" to only run the PHP workflow when the php cluster or its dependencies have changed in one of the commits. 2. Either create a separate PHP workflow or add the PHP windows testing to the current PHP workflow. Currently most of the workflows use the "Apache Netbeans" as the name. We should change the names to describe the workflow. Are these suggestions worth pursuing? --Christian
