Hi all, Potentially I'm ignorant/ don't know but how does the GitHub CI choose which tests on modules and subworkflows are performed? Do we have any documentation on that? Or a code snippet to mimic that behavior locally before opening PRs. @Gary Burnett might also be interesting for you ;)

The workflow is here: https://github.com/nf-core/modules/blob/master/.github/workflows/nf-test.yml

Hi Phil, Thanks a lot for the details! I will look into it. 🙂

nf-test has some native features now for this, you can use

nf-test test --smart-testing

which checks for changes since

HEAD^

, amongst some other features, check out the docs: https://www.nf-test.com/docs/cli/test/

Hi Adam, thanks a lot for the explanation. I indeed tried to mimic the CI behavior by using

--changes-since

{commit hash from my last fork sync}. I think my confusion came when the branch in my PR became out-of-date with the base branch...

Yep, we get this in nf-core/modules where if the branch isn't up to date you run 1 billion irrelevant tests party dead