We have a GitHub actions workflow that calls brew test-bot on all pull request and master branch commits, but it's behavior has changed from what I initially intended. I originally intended that the Actions CI should install any bottles that have changed and run brew test and brew audit, similar to the project-install-homebrew.bash script in release-tools.
- All
master branch builds fail since it is unable to detect variables showing what has changed since the last job.
- All pull request builds seem to be rebuilding bottles instead of testing the existing ones.
In both cases, we should only test formulae that have bottles, and if so, install, test, and audit them.
We have a GitHub actions workflow that calls
brew test-boton all pull request andmasterbranch commits, but it's behavior has changed from what I initially intended. I originally intended that the Actions CI should install any bottles that have changed and runbrew testandbrew audit, similar to the project-install-homebrew.bash script in release-tools.masterbranch builds fail since it is unable to detect variables showing what has changed since the last job.In both cases, we should only test formulae that have bottles, and if so, install, test, and audit them.