Description
Semaphore's Github pull_requests workflow has recently been optimized to run some jobs only when related files are actually changed (#765). However, the file and folder paths to be considered for detecting changes do not take into account some configuration files, thus preventing some jobs from running even when they should.
Additionally, recently ZK-Kit has further optimized the workflows:
- merging the
pull_requests and production workflows into 1: main
- sharing cached dependencies among jobs
Semaphore workflows therefore need to be updated with the above points in mind. This issue is supposed to be used to discuss these points and converge on a final solution to be adopted.
Description
Semaphore's Github
pull_requestsworkflow has recently been optimized to run some jobs only when related files are actually changed (#765). However, the file and folder paths to be considered for detecting changes do not take into account some configuration files, thus preventing some jobs from running even when they should.Additionally, recently ZK-Kit has further optimized the workflows:
pull_requestsandproductionworkflows into 1:mainSemaphore workflows therefore need to be updated with the above points in mind. This issue is supposed to be used to discuss these points and converge on a final solution to be adopted.