:mag: *Introducing `nf-diff`: Track and compare Ne...
# shameless-promo
m
πŸ” Introducing `nf-diff`: Track and compare Nextflow pipeline runs! Hey everyone! πŸ‘‹ When refactoring Nextflow pipelines or testing bug fixes, it’s often difficult to verify whether output files, execution metrics, or trace reports changed and by how much. I’ve been working on
nf-diff
, a dedicated Nextflow plugin that compares the output directory structure, metrics, process relationships and generated artifacts between two Nextflow runs. It helps you quickly spot unintended data drift, missing files, or unexpected changes across runs. πŸš€ πŸ› οΈ What
nf-diff
gives you:
β€’ Direct comparison of output directories and execution artifacts generated by Nextflow. β€’ Clear visual summaries of added, modified, or removed outputs and trace data. β€’ Lightweight CLI integration for local testing or custom pipelines. It supports many features and multiple output formats. I’m attaching the HTML report of a
nf-diff
I did here to showcase the plugin capabilities πŸ˜„ βš™οΈ Bonus β€” Use it in CI: I’ve also built the
nf-diff
GitHub Action
so you can run these output comparisons automatically on Pull Requests and see the results directly as PR comments! πŸ•ΈοΈ Official website: mribeirodantas.github.io/nf-diff/latest πŸ“Œ Core Project: github.com/mribeirodantas/nf-diff πŸ’‘ GitHub Action Demo & Live PR Examples: github.com/mribeirodantas/demo-nf-pipeline/pulls Give it a spin, star the repo if you find it useful, and let me know if you have any feedback or edge cases to test! Open to contributions! πŸ™Œ
⭐ 4
πŸ™‡ 2
πŸš€ 2
πŸ™Œ 1
πŸ‘ 1
message has been deleted
m
I like this
❀️ 1