Currently, in a PR, the main testing pipeline is run with the default settings i.e., without type checking, mutation tests and combination tests. However, currently specific parts of the pipeline can be triggered by commenting /type-check, /mutate, /combos (or /all-tests) respectively.
This, currently, does not update the check-suite within the PR though, the results have to be manually checked in the Actions tab.
Idea
Create a secondary pipeline, which triggers the check-suite with the configuration which steps are to be executed, thus the results are readily available in the PR.
Context
Currently, in a PR, the main testing pipeline is run with the default settings i.e., without type checking, mutation tests and combination tests. However, currently specific parts of the pipeline can be triggered by commenting
/type-check
,/mutate
,/combos
(or/all-tests
) respectively.This, currently, does not update the check-suite within the PR though, the results have to be manually checked in the Actions tab.
Idea
Create a secondary pipeline, which triggers the check-suite with the configuration which steps are to be executed, thus the results are readily available in the PR.
References