This adds two new standard workflows to this pipeline:
The new Nextflow configuration regression test Action from https://github.com/uclahs-cds/tool-Nextflow-action/pull/16. I've also added one regression test (copied from the NFTest cases). I make no claims that the output configuration is what is intended, but it is at least what is output given the current inputs.
For the documentation workflow, nothing should happen until this PR is merged, and then the documentation should be updated automatically on every update to main and every tag creation. After that is done I will go back and backfill docs for the existing releases.
[x] The name of the branch is meaningful and well formatted following the standards, using [AD_username (or 5 letters of AD if AD is too long)]-[brief_description_of_branch].
[x] I have set up or verified the branch protection rule following the github standards before opening this pull request.
[x] I have added my name to the contributors listings in the manifest block in the nextflow.config as part of this pull request; I am listed already, or do not wish to be listed. (This acknowledgement is optional.)
[x] I have added the changes included in this pull request to the CHANGELOG.md under the next release version or unreleased, and updated the date.
[ ] I have updated the version number in the metadata.yaml and manifest block of the nextflow.config file following semver, or the version number has already been updated. (Leave it unchecked if you are unsure about new version number and discuss it with the infrastructure team in this PR.)
[ ] I have tested the pipeline on at least one A-mini sample.
Description
This adds two new standard workflows to this pipeline:
For the documentation workflow, nothing should happen until this PR is merged, and then the documentation should be updated automatically on every update to main and every tag creation. After that is done I will go back and backfill docs for the existing releases.
Checklist
[x] I have read the code review guidelines and the code review best practice on GitHub check-list.
[x] I have reviewed the Nextflow pipeline standards.
[x] The name of the branch is meaningful and well formatted following the standards, using [AD_username (or 5 letters of AD if AD is too long)]-[brief_description_of_branch].
[x] I have set up or verified the branch protection rule following the github standards before opening this pull request.
[x] I have added my name to the contributors listings in the
manifest
block in thenextflow.config
as part of this pull request; I am listed already, or do not wish to be listed. (This acknowledgement is optional.)[x] I have added the changes included in this pull request to the
CHANGELOG.md
under the next release version or unreleased, and updated the date.[ ] I have updated the version number in the
metadata.yaml
andmanifest
block of thenextflow.config
file following semver, or the version number has already been updated. (Leave it unchecked if you are unsure about new version number and discuss it with the infrastructure team in this PR.)[ ] I have tested the pipeline on at least one A-mini sample.