mirror of
https://github.com/netdata/libbpf.git
synced 2026-11-05 17:30:15 +08:00
sync: document automated sync in SYNC.md
Describe what the libbpf-sync workflow does and what to do when it fails. Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Ihor Solodrai <ihor.solodrai@linux.dev>
This commit is contained in:
1 parent
c6a6fdb609
commit
85c0d575a4
1 file changed
+12
@@ -21,6 +21,18 @@ This document goes over the process of syncing libbpf sources from Linux repo
|
||||
to this Github repository. Feel free to contribute fixes and additions if you
|
||||
run into new problems not outlined here.
|
||||
|
||||
Automated sync
|
||||
--------------
|
||||
|
||||
The [libbpf-sync workflow](.github/workflows/libbpf-sync.yml) runs the sync
|
||||
monthly; to sync on demand, run it manually with `dry_run` disabled. If the
|
||||
sync needs no human input, the workflow opens a `libbpf-sync-*` PR. Approve
|
||||
its workflow runs to start libbpf CI, and push any CI fixes on top of it, as
|
||||
described below. No new sync is attempted while such a PR is open.
|
||||
|
||||
If the workflow run fails, sync manually following the rest of this document.
|
||||
The run's artifact has the sync log.
|
||||
|
||||
Setup expectations
|
||||
------------------
|
||||
|
||||
|
||||
Reference in new issue
Block a user