You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We may want to make sure to run some Linux kernel CI using this repository when a pull request is submitted and/or a change is pushed to master. I'd guess (but have not checked) that we could probably reuse large swaths of libbpf CI hooks to go about that.
The text was updated successfully, but these errors were encountered:
I think that ideally, we'd consolidate more of the workflow logic to begin with and then we could potentially just reuse the exact workflow by calling it.
On Wed, Nov 23, 2022 at 11:24 AM danielocfb ***@***.***> wrote:
I think that ideally, we'd consolidate more of the workflow logic to begin
with and then we could potentially just reuse the exact workflow by calling
it.
Wouldn’t the re-usable workflow do the trick?
https://docs.github.com/en/actions/using-workflows/reusing-workflows
Simplify its integration in kernel-patches/bpf, allow running linting on
kernel-patches/vmtest without having it getting pulled in the bpf repo.
Being able to pull it from libbpf/ci and have the tests run with minimal
change (assuming that this circulate dependency is not an issue).
We may want to make sure to run some Linux kernel CI using this repository when a pull request is submitted and/or a change is pushed to
master
. I'd guess (but have not checked) that we could probably reuse large swaths oflibbpf
CI hooks to go about that.The text was updated successfully, but these errors were encountered: