Skip to content
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

Explain we don't want MD5 checksums for versions.yml #1823

Merged
merged 4 commits into from
Jul 6, 2023
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions markdown/developers/modules.md
Original file line number Diff line number Diff line change
Expand Up @@ -126,6 +126,8 @@ We have implemented a number of commands in the `nf-core/tools` package to make

`md5sum` checks are the preferable choice of test to determine file changes, however, this may not be possible for all outputs generated by some tools e.g. if they include time stamps or command-related headers. Please do your best to avoid just checking for the file being present e.g. it may still be possible to check that the file contains the appropriate text snippets.

> Leave the `versions.yml` entry _without_ a MD5 checksum. Indeed its content will change every time we bump the version of the software.
mirpedrol marked this conversation as resolved.
Show resolved Hide resolved

8. Create a yaml file containing information required for module unit testing

```console
Expand Down