* Specify more guidelines on input channels
* Linting
* Updates based on code review
* Update README.md
* Fix broken sentence
* Describe CPU splitting
* Update README.md
Co-authored-by: Gregor Sturm <mail@gregor-sturm.de>
* More CPU examples
Co-authored-by: Gregor Sturm <mail@gregor-sturm.de>
* Update README
* Rename pytest_software.yml to pytest_modules.yml
* Rename main software directory to modules
* Remove deprecated modules
* Rename tests software to modules
* Replace paths for tests in pytest_modules.yml
* Replace software with modules in Github Actions
* Replace software with modules in main.nf tests
* Rename software to modules in test.yml
Running pytest with `--tag fastqc_single_end` does not work (it runs zero tests), as it appears that the tag name was changed to `fastqc` during the transition from underscores to slashes.
* Update README to include some git best practices
* correct linting errors
* extra info about returning to master and deleting the branch
* use rebase
* stress importance of rebase
* Update README to include some git best practices
* correct linting errors
* extra info about returning to master and deleting the branch
* Changed position of git commands
* move later git commands down the action list
* initial 'modules create' of minia
* fixed tests
* finished meta.yml
* fixed filters.yml
* resolved issues in pytest_software.yml
* add newline
* Update software/minia/main.nf
* fixing a bunch of module tests
* remove vscode
* fixed minia
* move test data directory to nf-core/test-datasets
* bump multiqc version
* remove the test data
* updated test data link
* update README
Co-authored-by: Harshil Patel <drpatelh@users.noreply.github.com>
* Add default output dir for modules that create indices
* Change path for index module test output
* Fix bowtie2/align tests
* Fixing bowtie/align tests
* Fix genomegenerate test
* Fixing README linting
* feature: add new issue template for creating new module
* Apply suggestions from code review
* Apply suggestions from code review
Co-authored-by: Kevin Menden <kevin.menden@live.com>
Co-authored-by: Kevin Menden <kevin.menden@live.com>