There's sometimes PR's opened which don't require integration testing. Such as changing docs. We can use the tj-actions/changed-files@v45 action to check which files changes and only run the tests if there is changes in the aries_cloudagent subdirectory.
For the ACA-Py specific BDD tests they use the demo agent so they should also be run on any demo subdirectory changes or docker subdirectory changes.
For the Scenario testing they should be run if there's any changes in the scenario subdirectory, and they also use the Dockerfile in the docker directory and should be run if there's changes to that file.
There's sometimes PR's opened which don't require integration testing. Such as changing docs. We can use the
tj-actions/changed-files@v45action to check which files changes and only run the tests if there is changes in thearies_cloudagentsubdirectory.For the
ACA-Py specific BDD teststhey use the demo agent so they should also be run on anydemosubdirectory changes ordockersubdirectory changes.For the
Scenario testingthey should be run if there's any changes in thescenariosubdirectory, and they also use the Dockerfile in thedockerdirectory and should be run if there's changes to that file.