- Major new feature - Validation of pipeline parameters [#426]
- The addition runs as soon as the pipeline launches and checks the pipeline input parameters two main things:
- No parameters are supplied that share a name with core Nextflow options (eg.
--resumeinstead of-resume) - Supplied parameters validate against the pipeline JSON schema (eg. correct variable types, required values)
- No parameters are supplied that share a name with core Nextflow options (eg.
- If either parameter validation fails or the pipeline has errors, a warning is given about any unexpected parameters found which are not described in the pipeline schema.
- This behaviour can be disabled by using
--validate_params false
- The addition runs as soon as the pipeline launches and checks the pipeline input parameters two main things:
- Added profiles to support the Charliecloud and Shifter container engines [#824]
- Fixed typo in nf-core-lint CI that prevented the markdown summary from being automatically posted on PRs as a comment.
- Changed default for
--inputfromdata/*{1,2}.fastq.gztonull, as this is now validated by the schema as a required value. - Removed support for
--nameparameter for custom run names.- The same functionality for MultiQC still exists with the core Nextflow
-nameoption.
- The same functionality for MultiQC still exists with the core Nextflow
- Added to template docs about how to identify process name for resource customisation
- added
nf-core modules removecommand to uninstall modules
- Fixed some bugs in the command line interface for
nf-core launchand improved formatting [#829] - New functionality for
nf-core downloadto make it compatible with DSL2 pipelines [#832]- Singularity images in module files are now discovered and fetched
- Direct downloads of Singularity images in python allowed (much faster than running
singularity pull) - Downloads now work with
$NXF_SINGULARITY_CACHEDIRso that pipelines sharing containers have efficient downloads
- Added new option
--fixto automatically correct some problems detected by linting - Added validation of default params to
nf-core schema lint[#823] - Added schema validation of GitHub action workflows to lint function [#795]
- Fixed bug in schema title and description validation
- Added second progress bar for conda dependencies lint check, as it can be slow [#299]
- Added new lint test to check files that should be unchanged from the pipeline.
v1.12.1 - Silver Dolphin - [2020-12-03]
- Finished switch from
$baseDirto$projectDiriniGenomes.confandmain.nf- Main fix is for
smail_fieldswhich was a bug introduced in the previous release. Sorry about that!
- Main fix is for
- Ported a number of small content tweaks from nf-core/eager to the template [#786]
- Better contributing documentation, more placeholders in documentation files, more relaxed markdownlint exceptions for certain HTML tags, more content for the PR and issue templates.
- Pipeline schema: make parameters of type
rangetonumber. [#738] - Respect
$NXF_HOMEwhen looking for pipelines withnf-core list[#798] - Swapped PyInquirer with questionary for command line questions in
launch.py[#726]- This should fix conda installation issues that some people had been hitting
- The change also allows other improvements to the UI
- Fix linting crash when a file deleted but not yet staged in git [#796]
v1.12 - Mercury Weasel - [2020-11-19]
- Updated
nf_coredocumentation generator for building https://nf-co.re/tools-docs/
- Make CI comments work with PRs from forks [#765]
- Branch protection and linting results should now show on all PRs
- Updated GitHub issue templates, which had stopped working
- Refactored GitHub Actions so that the AWS full-scale tests are triggered after docker build is finished
- DockerHub push workflow split into two - one for dev, one for releases
- Updated actions to no longer use
set-envwhich is now depreciating [#739] - Added config import for
test_fullinnextflow.config - Switched depreciated
$baseDirto$projectDir - Updated minimum Nextflow version to
20.04.10 - Make Nextflow installation less verbose in GitHub Actions [#780]
- Updated code to display colours in GitHub Actions log output
- Allow tests to pass with
devversion of nf-core/tools (previous failure due to base image version) - Lint code no longer tries to post GitHub PR comments. This is now done in a GitHub Action only.
v1.11 - Iron Tiger - [2020-10-27]
- Fix command error in
awstest.ymlGitHub Action workflow. - Allow manual triggering of AWS test GitHub Action workflows.
- Remove TODO item, which was proposing the usage of additional files beside
usage.mdandoutput.mdfor documentation. - Added a Podman profile, which enables Podman as container.
- Updated linting for GitHub actions AWS tests workflows.
- Made a base-level
Dockerfilea warning instead of failure - Added a lint failure if the old
bin/markdown_to_html.rscript is found - Update
richpackage dependency and use new markup escaping to change[[!]]back to[!]again
- Pipeline sync - fetch full repo when checking out before sync
- Sync - Add GitHub actions manual trigger option
v1.10.2 - Copper Camel (brought back from the dead) - [2020-07-31]
Second patch release to address some small errors discovered in the pipeline template. Apologies for the inconvenience.
- Fix syntax error in
/push_dockerhub.ymlGitHub Action workflow - Change
params.readPaths->params.input_pathsintest_full.config - Check results when posting the lint results as a GitHub comment
- This feature is unfortunately not possible when making PRs from forks outside of the nf-core organisation for now.
- More major refactoring of the automated pipeline sync
- New GitHub Actions matrix parallelisation of sync jobs across pipelines [#673]
- Removed the
--allbehaviour fromnf-core syncas we no longer need it - Sync now uses a new list of pipelines on the website which does not include archived pipelines [#712]
- When making a PR it checks if a PR already exists - if so it updates it [#710]
- More tests and code refactoring for more stable code. Hopefully fixes 404 error [#711]
v1.10.1 - Copper Camel (patch) - [2020-07-30]
Patch release to fix the automatic template synchronisation, which failed in the v1.10 release.
- Improved logging:
nf-core --log-file log.txtnow saves a verbose log to disk. - nf-core/tools GitHub Actions pipeline sync now uploads verbose log as an artifact.
- Sync - fixed several minor bugs, made logging less verbose.
- Python Rich library updated to
>=4.2.1 - Hopefully fix git config for pipeline sync so that commit comes from @nf-core-bot
- Fix sync auto-PR text indentation so that it doesn't all show as code
- Added explicit flag
--show-passedfornf-core lintinstead of taking logging verbosity
v1.10 - Copper Camel - [2020-07-30]
This release of nf-core/tools introduces a major change / new feature: pipeline schema.
These are JSON Schema files that describe all of the parameters for a given
pipeline with their ID, a description, a longer help text, an optional default value, a variable type
(eg. string or boolean) and more.
The files will be used in a number of places:
- Automatic validation of supplied parameters when running pipelines
- Pipeline execution can be immediately stopped if a required
paramis missing, or does not conform to the patterns / allowed values in the schema.
- Pipeline execution can be immediately stopped if a required
- Generation of pipeline command-line help
- Running
nextflow run <pipeline> --helpwill use the schema to generate a help text automatically
- Running
- Building online documentation on the nf-core website
- Integration with 3rd party graphical user interfaces
To support these new schema files, nf-core/tools now comes with a new set of commands: nf-core schema.
- Pipeline schema can be generated or updated using
nf-core schema build- this takes the parameters from the pipeline config file and prompts the developer for any mismatch between schema and pipeline.- Once a skeleton Schema file has been built, the command makes use of a new nf-core website tool to provide a user friendly graphical interface for developers to add content to their schema: https://nf-co.re/pipeline_schema_builder
- Pipelines will be automatically tested for valid schema that describe all pipeline parameters using the
nf-core schema lintcommand (also included as part of the mainnf-core lintcommand). - Users can validate their set of pipeline inputs using the
nf-core schema validatecommand.
In addition to the new schema commands, the nf-core launch command has been completely rewritten from
scratch to make use of the new pipeline schema. This command can use either an interactive command-line
prompt or a rich web interface to help users set parameters for a pipeline run.
The parameter descriptions and help text are fully used and embedded into the launch interfaces to make this process as user-friendly as possible. We hope that it's particularly well suited to those new to nf-core.
Whilst we appreciate that this new feature will add a little work for pipeline developers, we're excited at
the possibilities that it brings. If you have any feedback or suggestions, please let us know either here on
GitHub or on the nf-core #json-schema Slack channel.
We have adopted the use of the Black Python code formatter.
This ensures a harmonised code formatting style throughout the package, from all contributors.
If you are editing any Python code in nf-core/tools you must now pass the files through Black when
making a pull-request. See .github/CONTRIBUTING.md for details.
- Add
--publish_dir_modeparameter #585 - Isolate R library paths to those in container #541
- Added new style of pipeline parameters JSON schema to pipeline template
- Add ability to attach MultiQC reports to completion emails when using
mail - Update
output.mdand add in 'Pipeline information' section describing standard NF and pipeline reporting. - Build Docker image using GitHub Actions, then push to Docker Hub (instead of building on Docker Hub)
- Add Slack channel badge in pipeline README
- Allow multiple container tags in
ci.ymlif performing multiple tests in parallel - Add AWS CI tests and full tests GitHub Actions workflows
- Update AWS CI tests and full tests secrets names
- Added
macs_gsizefor danRer10, based on this post - Add information about config files used for workflow execution (
workflow.configFiles) to summary - Fix
markdown_to_html.pyto work with Python 2 and 3. - Change
params.reads->params.input - Change
params.readPaths->params.input_paths - Added a
.github/.dockstore.ymlconfig file for automatic workflow registration with dockstore.org
- Refactored PR branch tests to be a little clearer.
- Linting error docs explain how to add an additional branch protecton rule to the
branch.ymlGitHub Actions workflow. - Adapted linting docs to the new PR branch tests.
- Failure for missing the readme bioconda badge is now a warn, in case this badge is not relevant
- Added test for template
{{ cookiecutter.var }}placeholders - Fix failure when providing version along with build id for Conda packages
- New
--jsonand--markdownoptions to print lint results to JSON / markdown files - Linting code now automatically posts warning / failing results to GitHub PRs as a comment if it can
- Added AWS GitHub Actions workflows linting
- Fail if
params.inputisn't defined. - Beautiful new progress bar to look at whilst linting is running and awesome new formatted output on the command line 😍
- All made using the excellent
richpython library - check it out!
- All made using the excellent
- Tests looking for
TODOstrings should now ignore editor backup files. #477
- Added CI test to check for PRs against
masterin tools repo - CI PR branch tests fixed & now automatically add a comment on the PR if failing, explaining what is wrong
- Move some of the issue and PR templates into HTML
<!-- comments -->so that they don't show in issues / PRs
- Describe alternative installation method via conda with
conda env create - nf-core/tools version number now printed underneath header artwork
- Bumped Conda version shipped with nfcore/base to 4.8.2
- Added log message when creating new pipelines that people should talk to the community about their plans
- Fixed 'on completion' emails sent using the
mailcommand not containing body text. - Improved command-line help text for nf-core/tools
nf-core listnow hides archived pipelines unless--show_archivedflag is set- Command line tools now checks if there is a new version of nf-core/tools available
- Disable this by setting the environment variable
NFCORE_NO_VERSION_CHECK, eg.export NFCORE_NO_VERSION_CHECK=1
- Disable this by setting the environment variable
- Better command-line output formatting of nearly all
nf-corecommands usingrich
v1.9 - Platinum Pigeon - [2020-02-20]
- Travis CI tests are now deprecated in favor of GitHub Actions within the pipeline template.
nf-core bump-versionsupport has been removed for.travis.ymlnf-core lintnow fails if a.travis.ymlfile is found
- Ported nf-core/tools Travis CI automation to GitHub Actions.
- Fixed the build for the nf-core/tools API documentation on the website
- Rewrote the documentation markdown > HTML conversion in Python instead of R
- Fixed rendering of images in output documentation #391
- Removed the requirement for R in the conda environment
- Make
params.multiqc_configgive an additional MultiQC config file instead of replacing the one that ships with the pipeline - Ignore only
tests/andtesting/directories in.gitignoreto avoid ignoringtest.configconfiguration file - Rephrase docs to promote usage of containers over Conda to ensure reproducibility
- Stage the workflow summary YAML file within MultiQC work directory
- Removed linting for CircleCI
- Allow any one of
params.readsorparams.inputorparams.designbefore warning - Added whitespace padding to lint error URLs
- Improved documentation for lint errors
- Allow either
>=or!>=in nextflow version checks (the latter exits with an error instead of just warning) #506 - Check that
manifest.versionends indevand throw a warning if not- If running with
--releasecheck the opposite and fail if not
- If running with
- Tidied up error messages and syntax for linting GitHub actions branch tests
- Add YAML validator
- Don't print test results if we have a critical error
- Fix automatic synchronisation of the template after releases of nf-core/tools
- Improve documentation for installing
nf-core/tools - Replace preprint by the new nf-core publication in Nature Biotechnology 🍾
- Use
stderrinstead ofstdoutfor header artwork - Tolerate unexpected output from
nextflow configcommand - Add social preview image
- Added a release checklist for the tools repo
v1.8 - Black Sheep - [2020-01-27]
- GitHub Actions CI workflows are now included in the template pipeline
- Please update these files to match the existing tests that you have in
.travis.yml
- Please update these files to match the existing tests that you have in
- Travis CI tests will be deprecated from the next
toolsrelease - Linting will generate a warning if GitHub Actions workflows do not exist and if applicable to remove Travis CI workflow file i.e.
.travis.yml.
- Refactored the template synchronisation code to be part of the main nf-core tool
nf-core bump-versionnow also bumps the version string of the exported conda environment in the Dockerfile- Updated Blacklist of synced pipelines
- Ignore pre-releases in
nf-core list - Updated documentation for
nf-core download - Fixed typo in
nf-core launchfinal command - Handle missing pipeline descriptions in
nf-core list - Migrate tools package CI to GitHub Actions
- Adjusted linting to enable
patchbranches from being tested - Warn if GitHub Actions workflows do not exist, warn if
.travis.ymland circleCI are there - Lint for
Singularityfile and raise error if found #458 - Added linting of GitHub Actions workflows
linting.yml,ci.ymlandbranch.yml - Warn if pipeline name contains upper case letters or non alphabetical characters #85
- Make CI tests of lint code pass for releases
- Fixed incorrect paths in iGenomes config as described in issue #418
- Fixed incorrect usage of non-existent parameter in the template #446
- Add UCSC genomes to
igenomes.configand add paths to all genome indices - Change
maxMultiqcEmailFileSizeparameter tomax_multiqc_email_size - Export conda environment in Docker file #349
- Change remaining parameters from
camelCasetosnake_case#39--singleEndto--single_end--igenomesIgnoreto--igenomes_ignore- Having the old camelCase versions of these will now throw an error
- Add
autoMounts=trueto default singularity profile - Add in
markdownlintchecks that were being ignored by default - Disable ansi logging in the travis CI tests
- Move
paramssection frombase.configtonextflow.config - Use
envscope to exportPYTHONNOUSERSITEinnextflow.configto prevent conflicts with host Python environment - Bump minimum Nextflow version to
19.10.0- required to properly useenvscope innextflow.config - Added support for nf-tower in the travis tests, using public mailbox nf-core@mailinator.com
- Add link to Keep a Changelog and Semantic Versioning to CHANGELOG
- Adjusted
.travis.ymlchecks to allow forpatchbranches to be tested - Add Python 3.7 dependency to the
environment.ymlfile - Remove
awsbatchprofile cf nf-core/configs#71 - Make
scrape_software_versions.pycompatible with Python3 to enable miniconda3 in base image PR - Add GitHub Actions workflows and respective linting
- Add
NXF_ANSI_LOGas global environment variable to template GitHub Actions CI workflow - Fixed global environment variable in GitHub Actions CI workflow
- Add
--awscliparameter - Add
README.txtpath for genomes inigenomes.confignf-core/atacseq#75 - Fix buggy ANSI codes in pipeline summary log messages
- Add a
TODOline in the new GitHub Actions CI test files
- Use miniconda3 instead of miniconda for a Python 3k base environment
- If you still need Python 2 for your pipeline, add
conda-forge::python=2.7.4to the dependencies in yourenvironment.yml
- If you still need Python 2 for your pipeline, add
- Update conda version to 4.7.12
- Updated Base Dockerfile to Conda 4.7.10
- Entirely switched from Travis-Ci.org to Travis-Ci.com for template and tools
- Improved core documentation (
-profile)
v1.7 - Titanium Kangaroo - [2019-10-07]
- The tools
createcommand now sets up aTEMPLATEand adevbranch for syncing - Fixed issue 379
- nf-core launch now uses stable parameter schema version 0.1.0
- Check that PR from patch or dev branch is acceptable by linting
- Made code compatible with Python 3.7
- The
downloadcommand now also fetches institutional configs from nf-core/configs - When listing pipelines, a nicer message is given for the rare case of a detached
HEADref in a locally pulled pipeline. #297 - The
downloadcommand can now compress files into a single archive. nf-core createnow fetches a logo for the pipeline from the nf-core website- The readme should now be rendered properly on PyPI.
- Can now sync a targeted pipeline via command-line
- Updated Blacklist of synced pipelines
- Removed
chipseqfrom Blacklist of synced pipelines - Fixed issue #314
- If the container slug does not contain the nf-core organisation (for example during development on a fork), linting will raise a warning, and an error with release mode on
- Add new code for Travis CI to allow PRs from patch branches too
- Fix small typo in central readme of tools for future releases
- Small code polishing + typo fix in the template main.nf file
- Header ANSI codes no longer print
[2mto console when using-with-ansi - Switched to yaml.safe_load() to fix PyYAML warning that was thrown because of a possible exploit
- Add
nf-corecitation - Add proper
nf-corelogo for tools - Add
Quick Startsection to main README of template - Fix Docker RunOptions to get UID and GID set in the template
Dockerfilenow specifically uses the proper release tag of the nfcore/base image- Use
fileinstead ofnew Fileto avoid weird behavior such as making ans3:/directory locally when using an AWS S3 bucket as the--outdir. - Fix workflow.onComplete() message when finishing pipeline
- Update URL for joining the nf-core slack to https://nf-co.re/join/slack
- Add GitHub Action for CI and Linting
- Increased default time limit to 4h
- Add direct link to the pipeline slack channel in the contribution guidelines
- Add contributions and support heading with links to contribution guidelines and link to the pipeline slack channel in the main README
- Fix Parameters JSON due to new versionized structure
- Added conda-forge::r-markdown=1.1 and conda-forge::r-base=3.6.1 to environment
- Plain-text email template now has nf-core ASCII artwork
- Template configured to use logo fetched from website
- New option
--email_on_failwhich only sends emails if the workflow is not successful - Add file existence check when checking software versions
- Fixed issue #165 - Use
checkIfExists - Consistent spacing for
ifstatements - Add sensible resource labels to
base.config
- Bump
condato 4.6.14 in base nf-core Dockerfile - Added a Code of Conduct to nf-core/tools, as only the template had this before
- TravisCI tests will now also start for PRs from
patchbranches, to allow fixing critical issues without making a new major release
v1.6 - Brass Walrus - [2020-04-09]
- Code refactoring to make the script more readable
- No travis build failure anymore on sync errors
- More verbose logging
- awsbatch
work-dirchecking moved to nextflow itself. Removed unsatisfiable check in main.nf template. - Fixed markdown linting
- Tools CI testing now runs markdown lint on compiled template pipeline
- Migrated large portions of documentation to the nf-core website
- Removed Gitter references in
.github/directories fortools/and pipeline template. - Changed
scrape_software_versions.pyto output.csvfile - Added
export_plotsparameter to multiqc config - Corrected some typos as listed here to Guidelines
- Drop nf-core/rnaseq from
blacklist.jsonto make template sync available - Updated main help command to sort the subcommands in a more logical order
- Updated readme to describe the new
nf-core launchcommand - Fix bugs in
nf-core download- The latest release is now fetched by default if not specified
- Downloaded pipeline files are now properly executable.
- Fixed bugs in
nf-core list- Sorting now works again
- Output is partially coloured (better highlighting out of date pipelines)
- Improved documentation
- Fixed bugs in
nf-core lint- The order of conda channels is now correct, avoiding occasional erroneous errors that packages weren't found (#207)
- Allow edge versions in nf-core pipelines
- Add reporting of ignored errored process
- As a solution for #103)
- Add Bowtie2 and BWA in iGenome config file template
v1.5 - Iron Shark - [2019-03-13]
- Dropped Singularity file
- Summary now logs details of the cluster profile used if from nf-core/configs
- Dockerhub is used in favor of Singularity Hub for pulling when using the Singularity profile
- Changed default container tag from latest to dev
- Brought the logo to life
- Change the default filenames for the pipeline trace files
- Remote fetch of nf-core/configs profiles fails gracefully if offline
- Remove
params.containerand just directly defineprocess.containernow - Completion email now includes MultiQC report if not too big
params.genomeis now checked if set, to ensure that it's a valid iGenomes key- Together with nf-core/configs, helper function now checks hostname and suggests a valid config profile
awsbatchexecutor requires thetracedirnot to be set to ans3bucket.
-
New
nf-core launchcommand to interactively launch nf-core pipelines from command-line- Works with a
parameters.settings.jsonfile shipped with each pipeline - Discovers additional
paramsfrom the pipeline dynamically
- Works with a
-
Drop Python 3.4 support
-
nf-core listnow only shows a value for "is local latest version" column if there is a local copy. -
Lint markdown formatting in automated tests
- Added
markdownlint-clifor checking Markdown syntax in pipelines and tools repo
- Added
-
Syncing now reads from a
blacklist.jsonin order to exclude pipelines from being synced if necessary. -
Added nf-core tools API description to assist developers with the classes and functions available.
- Docs are automatically built by Travis CI and updated on the nf-co.re website.
-
Introduced test for filtering remote workflows by keyword.
-
Build tools python API docs
- Use Travis job for api doc generation and publish
-
nf-core bump-versionnow stops before making changes if the linting fails -
Code test coverage
- Introduced test for filtering remote workflows by keyword
-
Linting updates
- Now properly searches for conda packages in default channels
- Now correctly validates version pinning for packages from PyPI
- Updates for changes to
process.containerdefinition
- Bump
condato 4.6.7 in base nf-core Dockerfile
v1.4 - Tantalum Butterfly - [2018-12-12]
- Institutional custom config profiles moved to github
nf-core/configs- These will now be maintained centrally as opposed to being shipped with the pipelines in
conf/ - Load
base.configby default for all profiles - Removed profiles named
standardandnone - Added parameter
--igenomesIgnoresoigenomes.configis not loaded if parameter clashes are observed - Added parameter
--custom_config_versionfor custom config version control. Can use this parameter to provide commit id for reproducibility. Defaults tomaster - Deleted custom configs from template in
conf/directory i.e.uzh.config,binac.configandcfc.config
- These will now be maintained centrally as opposed to being shipped with the pipelines in
multiqc_configandoutput_mdare now put into channels instead of using the files directly (see issue #222)- Added
local.mdto cookiecutter template indocs/configuration/. This was referenced inREADME.mdbut not present. - Major overhaul of docs to add/remove parameters, unify linking of files and added description for providing custom configs where necessary
- Travis: Pull the
devtagged docker image for testing - Removed UPPMAX-specific documentation from the template.
- Make Travis CI tests fail on pull requests if the
CHANGELOG.mdfile hasn't been updated - Minor bugfixing in Python code (eg. removing unused import statements)
- Made the web requests caching work on multi-user installations
- Handle exception if nextflow isn't installed
- Linting: Update for Travis: Pull the
devtagged docker image for testing
v1.3 - Citreous Swordfish - [2018-11-21]
nf-core createcommand line interface updated- Interactive prompts for required arguments if not given
- New flag for workflow author
- Updated channel order for bioconda/conda-forge channels in environment.yaml
- Increased code coverage for sub command
createandlicenses - Fixed nasty dependency hell issue between
pytestandpypackage in Python 3.4.x - Introduced
.coveragercfor pytest-cov configuration, which excludes the pipeline template now from being reported - Fix 189: Check for given conda and PyPi package dependencies, if their versions exist
- Added profiles for
cfc,binac,uzhthat can be synced across pipelines- Ordering alphabetically for profiles now
- Added
pip install --upgrade pipto.travis.ymlto update pip in the Travis CI environment
v1.2 - [2018-10-01]
- Updated the
nf-core releasecommand- Now called
nf-core bump-versionsinstead - New flag
--nextflowto change the required nextflow version instead
- Now called
- Template updates
- Simpler installation of the
nf-corehelper tool, now directly from PyPI - Bump minimum nextflow version to
0.32.0- required for built inmanifest.nextflowVersioncheck and access toworkflow.manifestvariables from within nextflow scripts - New
withNamesyntax for configs - Travis tests fail if PRs come against the
masterbranch, slightly refactored - Improved GitHub contributing instructions and pull request / issue templates
- Simpler installation of the
- New lint tests
.travis.ymltest for PRs made against themasterbranch- Automatic
--releaseoption not used if the travis repo isnf-core/tools - Warnings if depreciated variables
params.versionandparams.nf_required_versionare found
- New
nf-core licencessubcommand to show licence for each conda package in a workflow nf-core listnow has options for sorting pipeline nicely- Latest version of conda used in nf-core base docker image
- Updated PyPI deployment to correctly parse the markdown readme (hopefully!)
- New GitHub contributing instructions and pull request template
v1.1 - [2018-08-14]
Very large release containing lots of work from the first nf-core hackathon, held in SciLifeLab Stockholm.
- The Cookiecutter template has been merged into tools
- The old repo above has been archived
- New pipelines are now created using the command
nf-core create - The nf-core template and associated linting are now controlled under the same version system
- Large number of template updates and associated linting changes
- New simplified cookiecutter variable usage
- Refactored documentation - simplified and reduced duplication
- Better
manifestvariables instead ofparamsfor pipeline name and version - New integrated nextflow version checking
- Updated travis docker pull command to use tagging to allow release tests to pass
- Reverted Docker and Singularity syntax to use
ENVhack again
- Improved Python readme parsing for PyPI
- Updated Travis tests to check that the correct
devbranch is being targeted - New sync tool to automate pipeline updates
- Once initial merges are complete, a nf-core bot account will create PRs for future template updates
v1.0.1 - [2018-07-18]
The version 1.0 of nf-core tools cannot be installed from PyPi. This patch fixes it, by getting rid of the requirements.txt plus declaring the dependent modules in the setup.py directly.
v1.0 - [2018-06-12]
Initial release of the nf-core helper tools package. Currently includes four subcommands:
nf-core list: List nf-core pipelines with local infonf-core download: Download a pipeline and singularity containernf-core lint: Check pipeline against nf-core guidelinesnf-core release: Update nf-core pipeline version number