OK, just realizing a low-tech way this has been done in my experience: have
a workflow that goes red unless the commit / PR message to say something
like "TESTED=link to workflow run". I don't love it, and it is easy to get
lazy and circumvent, but I can see why it is what people chose to do.
A va
I actually don't think GitHub supports path filters for required checks, so
you can't say something like "check X is only required if path Y or Z are
modified", you can only say "check X is required". I'm not 100% sure on
this, but it matches my memory and I could neither find docs with that
featu
>From our other thread I had a thought about our "only on request" tests.
Today, in theory:
- The lightweight tests run automatically based on path matching. This is
an approximate implementation of the ideal of running based on whether they
could impact a test signal.
- Heavyweight (and more f
