When PR checks run, they should only run changes against files that have changed.
Specifically, I mean that if the Containerfile is changed and no go-code is changed, then the image should be built and those tests should run.
Or conversely, if say the personalization feature is updated to fix a bug, the container image build checks should be skipped.
The goal of this is to make PR checks run faster.
However, this should ideally be augmented by release-blocking tests that can test everything end to end, so that we don't accidentally introduce regressions.
When PR checks run, they should only run changes against files that have changed.
Specifically, I mean that if the Containerfile is changed and no go-code is changed, then the image should be built and those tests should run.
Or conversely, if say the
personalizationfeature is updated to fix a bug, the container image build checks should be skipped.The goal of this is to make PR checks run faster.
However, this should ideally be augmented by release-blocking tests that can test everything end to end, so that we don't accidentally introduce regressions.