Federico Di Pierro

So, after we removed the `kernels` branch, the `git clone --mirror` being made by `hook` plugin is now at ~75MB: ``` git clone --mirror https://github.com/falcosecurity/kernel-crawler Clone nel repository spoglio 'kernel-crawler.git'...

Using git, it will be done like so: ``` git filter-branch -f --index-filter "git rm -rf --cached --ignore-unmatch kernels/" HEAD git push origin HEAD --force-with-lease ```

So, the work was done; see for example this `main` commit: https://github.com/falcosecurity/kernel-crawler/commit/4438279c57e9931129a16e3b124275fe62ef443f But the end result is a bit different than expected, sizing around ~45MB: ``` git clone --mirror https://github.com/falcosecurity/kernel-crawler...

For reference, a `git clone --mirror` of libs accounts for ~35MB. There are no tags nor stale branches in kernel-crawler with big jsons; i don't really get this.

So, it seems `json`s are still referenced somewhere (of course): ``` git rev-list --objects --all | grep json 177bdb29d7cb55dd4505fcad7a0007bfe61856d0 kernels/aarch64/list.json 965ad4147108c5029395e898ccf461ba041c005b kernels/x86_64/list.json 7b28341c4ac53ab817104075cd62af1b2f871ce0 kernels/aarch64/list.json 7cc73e95ff22468866340e0506d64b228a53f696 kernels/x86_64/list.json 7ada52e6b02702dae8e1204b4e45ebde01514c93 kernels/aarch64/list.json 9de80130013a3020e23ead46f53a5df954d7eebe kernels/x86_64/list.json...

> So, it seems jsons are still referenced somewhere (of course): So, it seems like these might be related to the number of `json pushing` PRs that were opened to...

/remove-lifecycle stale

/remove-lifecycle stale

/hold Last versions of prow are killing jobs triggering...need to investigate.

Tackled second point here: https://github.com/falcosecurity/libs/pull/1745