chore(ci): Run test actions only when relevant code changed for website, backend #1695
Conversation
corneliusroemer
changed the title
There was a problem hiding this comment.
Do the website tests never touch the config files generated from kubernetes? (My instinct is that they indeed don't, but not totally sure)
Generally I'm not that worried about a bit of pointless CI especially when it's free (I find it quite useful as a control for things that do change the code), so am ambivalent here, but happy to go for it if people want it
Oh yeah I guess we can tell from these workflows that they don't |
|
I just think it's worth thinking about whether we'd have been as confident that we had flaky tests without pointless CI |
Fair point, though we can always trigger CI runs on main, we can reenable if we feel it becomes hard to tell flakiness apart |
Summary
Run backend and website test actions only when relevant code changed for backend, website respectively