Issue #18 had me thinking that the current way of reviewing the tests results and update the reference reports is not optimal.
The best way to do so would be to trigger a github action that will perform a PR.
Through the PR it would be much easier to assess which files were impacted and how, then accept the update if relevant
Issue #18 had me thinking that the current way of reviewing the tests results and update the reference reports is not optimal. The best way to do so would be to trigger a github action that will perform a PR. Through the PR it would be much easier to assess which files were impacted and how, then accept the update if relevant