We have several very expensive CI jobs that run our test suite for the function-evaluator. When merging, because our repos are FF-only, there is no difference between the circumstances, so we can rely on the status from those jobs, and only run the publish jobs, but we currently re-run everything.

There's a rules modifier to not run the publish jobs except after merge; presumably we could invert it somehow for the other jobs, except those that build assets for the publish jobs?