Run sync-kernel.sh with stdin from /dev/null, so that any prompt asking
for human input fails the sync.
The exit code of sync-kernel.sh isn't reliable (e.g., it exits with 0
when interrupted), so tell from its output whether the sync went
through or there was nothing to sync.
On success, leave a bundle with the sync branch, patches and a pull
request description with the sync log in the output directory.
Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Ihor Solodrai <ihor.solodrai@linux.dev>
Set up a Linux repo the way sync-kernel.sh expects it: HEAD at
bpf-next's master and a bpf-master branch at bpf's master.
Fetch full history of both trees from the kernel-patches/bpf mirror on
GitHub, which is more reliable than git.kernel.org. The mirror may lag
behind, so don't require its branches to match git.kernel.org exactly,
only check that they're in the history of the master branches there.
Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Ihor Solodrai <ihor.solodrai@linux.dev>
Automatically comment on and close master-targeted pull requests that
touch kernel-synchronized libbpf paths. Keep mirror-only and unknown
paths open, with a github-only label for maintainer overrides.
Signed-off-by: Ihor Solodrai <ihor.solodrai@linux.dev>
Ihor Solodrai