On Thu, Apr 18, 2024 at 04:04:10PM -0600, Andreas Dilger wrote: > > I've never used Github actions for this. If I fork tytso/e2fsprogs and > push to adilger/e2fsprogs, are those actions automated already with a > config file inside the repo, or do I need to set that up myself? Github actions should be enabled by default (although enterprise accounts can have the default changed or prohibited by the enterprise administrator's policy). The config file is checked into the repo at .github/workflows/ci.yml so if you fork the repo, you should get it. > PS: the kernel.org repo looks like it has not been updated in 4 months, > despite emails that you have landed patches. I was pulling from there > and didn't notice until now that you have been pushing only to github. I don't update kernel.org as frequently as github, but I suspect the issue is that you were probably looking at the master branch, and the updates were going on the next branch. When I'm processing a large number of patches, sometimes I don't update master until I'm really confident everything is in great shape to update the master branch to point at next. It's just that April has been super crazy busy me for me, so master lagged next by a few weeks. Cheers, - Ted
