nf-core / nf-core/modules

Update the `meta.yml` of subworkflows

Open
#6,737 1 comment 0 reactions 1 assignee View on GitHub

@muneebdev7 is already working on this.

Since Nov 23, 2024.

  • #6864 by @mirpedrol — merged
good first issue subworkflows update subworkflow
Dominant language
Nextflow
Stars
429
Forks
1.1k
Avg merge
1d 6h
Merged PRs (30d)
153

Description

The meta.yml of subworkflows should have the proper structure descirbing the structure of input and output channels.

A new flag --fix has been added to nf-core/tools v3.0.0 to help you restructure these files, but as the structure of channels can't be infered from the main.nf of the subworkflows, some manual work is required.

How To

  1. Make sure to use nf-core/tools v3.0.2
  2. Run the linting command with the --fix flag:
nf-core subworkflows lint --fix <subworkflow_name>
  1. Manually update the information of input and output channels

You can have a look to an example PR updating some of the subworkflows for reference.

List of subworkflows

If you plan to work on updating one of the subworkflows, please edit this message and add your github handle next to it to assign it to you.

  • bam_cnv_wisecondorx
  • bam_create_som_pon_gatk
  • bam_dedup_stats_samtools_umicollapse
  • bam_dedup_stats_samtools_umitools
  • bam_docounts_contamination_angsd
  • bam_markduplicates_picard
  • bam_markduplicates_samtools
  • bam_ngscheckmate
  • bam_qc_picard
  • bam_rseqc
  • bam_sort_stats_samtools (@mirpedrol)
  • bam_split_by_region (@mirpedrol)
  • bam_stats_mirna_mirtop (@mirpedrol)
  • bam_stats_samtools
  • bam_subsampledepth_samtools (@muneebdev7)
  • bam_tumor_normal_somatic_variant_calling_gatk
  • bam_tumor_normal_somatic_variant_calling_strelka
  • bam_tumor_only_somatic_variant_calling_gatk (@muneebdev7)
  • bam_variant_calling_sort_freebayes_bcftools (@muneebdev7)
  • bam_variant_demix_boot_freyja (@muneebdev7)
  • bcl_demultiplex (@muneebdev7)
  • bed_scatter_bedtools
  • bedgraph_bedclip_bedgraphtobigwig
  • deepvariant (@muneebdev7)
  • fasta_binning_concoct (@muneebdev7)
  • fasta_build_add_kraken2
  • fasta_build_add_kraken2_bracken
  • fasta_clean_fcs (@muneebdev7)
  • fasta_explore_search_plot_tidk (@muneebdev7)
  • fasta_hmmsearch_rank_fastas (@muneebdev7)
  • fasta_index_dna (@muneebdev7)
  • fasta_newick_epang_gappa (@muneebdev7)
  • fastq_align_bamcmp_bwa (@muneebdev7)
  • fastq_align_bowtie2 (@muneebdev7)
  • fastq_align_bwa (@muneebdev7)
  • fastq_align_bwaaln (@muneebdev7)
  • fastq_align_chromap (@muneebdev7)
  • fastq_align_dna (@muneebdev7)
  • fastq_align_hisat2 (@muneebdev7)
  • fastq_align_mapad (@muneebdev7)
  • fastq_align_star
  • fastq_contam_seqtk_kraken (@muneebdev7
  • fastq_create_umi_consensus_fgbio (@muneebdev7)
  • fastq_download_prefetch_fasterqdump_sratools (@muneebdev7)
  • fastq_extract_kraken_krakentools (@muneebdev7)
  • fastq_fastqc_umitools_fastp (@muneebdev7)
  • fastq_fastqc_umitools_trimgalore (@muneebdev7)
  • fastq_find_mirna_mirdeep2 (@muneebdev7)
  • fastq_ngscheckmate (@muneebdev7)
  • fastq_qc_trim_filter_setstrandedness (@muneebdev7)
  • fastq_subsample_fq_salmon (@muneebdev7)
  • fastq_taxonomic_profile_metaphlan (@muneebdev7)
  • fastq_trim_fastp_fastqc (@muneebdev7)
  • homer/groseq (@muneebdev7)
  • initialise
  • mmseqs_contig_taxonomy
  • multiple_impute_glimpse2 (@muneebdev7)
  • preprocess_rnaseq (@muneebdev7)
  • quantify_pseudo_alignment (@muneebdev7)
  • utils_nextflow_pipeline (@muneebdev7)
  • utils_nfcore_pipeline (@muneebdev7)
  • utils_nfschema_plugin (@muneebdev7)
  • utils_nfvalidation_plugin
  • vcf_annotate_ensemblvep (@muneebdev7)
  • vcf_annotate_ensemblvep_snpeff
  • vcf_annotate_snpeff (@muneebdev7)
  • vcf_extract_relate_somalier
  • vcf_gather_bcftools (@muneebdev7)
  • vcf_impute_glimpse
  • vcf_phase_shapeit5 (@muneebdev7)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.