The easiest way to use visual regression tests is to have a computer run them for you automatically. This task proposes adding a non-blocking CI job to the Vector repo that runs on each patch set made to Vector. If that goes well, other repos could be added.
It would run something like the following which would compare master against the change on top of master:
```
./pixel.js reference && ./pixel.js -c <Change-Id of Gerrit Patch>
```
If that command exits with `0`, the job passes. If it exits with something else, it fails. However, failures shouldn't block merging and should only be seen as flags that need discretionary review.
[[ https://github.com/nicholasray/pixel | Pixel ]] already does a [[ https://github.com/nicholasray/pixel/blob/963ff02c89bac888c6d078c4480e928b41ac69e3/.github/workflows/push.yml#L28-L31 | similar command for commits made to it ]]:
== Acceptance Criteria
[] Each Gerrit patch set made to Vector runs a command that compares master against that change/changes on top of master.
[] If the change includes dependencies that Pixel doesn't support, the job can be skipped.