-
Notifications
You must be signed in to change notification settings - Fork 438
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: Skip nf-test on docs changes #1761
Conversation
Co-authored-by: jfy133 <jfy133@users.noreply.github.com>
Warning Newer version of the nf-core template is available. Your pipeline is using an old version of the nf-core template: 3.0.2. For more documentation on how to update your pipeline, please see the nf-core documentation and Synchronisation documentation. |
|
The tests still ran though, no? |
Co-authored-by: Maxime U Garcia <max.u.garcia@gmail.com>
This modified a GitHub action yml not a doc 😜 |
Oh haha fair, but maybe worth modifying a doc as a test? 😬 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CHANGELOG?
First, happy to update it. But that request brought up a bigger question for me. IMO the CI change doesn't affect end users. Most developers aren't going to notice this one. Almost feels like we need a separate changelog or developers or call the git log good enough. I personally vote we don't update the changelog unless it's changing the user experience. Didn't flags, different tools so expect a different result. |
nuh, these kind of DX related changes shouldn't occur so often and don't really fill up the changelog, so better to add it there then to never mention it 🙂 (also might help other devs to discover these changes) |
Skips nf-test on any docs changes.
We can probably cut
docs/**
if we want to save lines 🙃