Federico Di Pierro

I see 2 main paths forward: * open a PR on kubernetes Prow to properly fetch changed files through git client using `before` and `after` refs from Push github event:...

Adding 2 more possible "fixes": * Run the update-kernels workflow daily instead of weekly: running it more frequently will generate less diff thus we would be more confident that all...

> split our workflow to open up a PR on test-infra for each crawled distro; this does not require any change to Prow (so, much quicker fix), but at the...

A short term solution would be to change all post submit triggers to trigger to any change to `driverkit/config/...` folder, ie from this: ``` run_if_changed: '^driverkit/config/[a-z0-9.+-]{5,}/x86_64/almalinux_.+' ``` to this: ```...

> In this case, we would trigger ALL jobs everytime, even for unmodified configs, then each job would build its own configs. We could also let the entrypoint of each...

> What about instead of reducing the granularity of the grid to increase the jobs frequency as you suggested, from weekly to one every two days for example That would...

> PS: in any case IMHO are both short term solutions. Agree btw :/

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle stale