Question: since I have repo superpowers, I could merge rnaseq PRs where the CI has previously passed and I'm just doing things like updating changelogs, thereby saving polar bears? I have refrained from doing so because folks might not take kindly.... but.. polar bears. Will folks yell at me if I do that sort of thing? I promise not to do it with code changes, and hope that my good behaviour even while in receipt of those powers proves my good faith 😄

sure sounds good. but let at least pre-commit pass, to not introduce any errors in the changelog 😉

is there a way on a single PR to only trigger new tests if the relevant files are touched? I know we can do it for a PR in general.

you mean only run some parts of a CI workflow based on the file path?

For general PRs we are triggering only a subset of tests in sarek if relevant files are touched @Maxime Garcia Help! where did you define this? What I mean, for a specific PR would this work on commit level. Let's say you changed the main.nf -> all tests are triggered all come back green. Then the changelog is updated -> only trigger linting because only an md file was touched that doesn't touch the main and it previously had green ticks

nf-test does that natively

CI tests always run on a PR level, not commit level

sadpanda that be nice by Github to implement 🌳

I guess it would get complicated if you're trying to keep track of what passed and didn't on the branch, you could cancel a test on a big changeset, push a commit to a .md and call it a pass? You'd have to somehow record that all the changes were tested and passed somewhere in the history. It wouldn't be trivial

(compared to all the LLM interferences in each PR, the CI has a rather low impact, i would say)

rnaseq's test suite has become quite substantial. I've tried to cut it back at times, but still

GitHub already has it - it runs CI either on commit or on PR. Running on commit is dangerous as it can pass there but then fail on merge, as it's effectively not the same code.

I'll make sure to cancel them as well then 🙂

You can also use [skip ci] when commiting only changelog changes to avoid triggering the CI again: https://docs.github.com/en/actions/how-tos/manage-workflow-runs/skip-workflow-runs

True, I always forget this!