|
| 1 | +# nf-core related commands for espanso |
| 2 | + |
| 3 | +## What is nf-core? |
| 4 | + |
| 5 | +[nf-core](https://nf-co.re/) is a community effort for building high-quality, reproducible bioinformatics pipelines with Nextflow. |
| 6 | +It provides: |
| 7 | + |
| 8 | +- Standardized pipeline structure |
| 9 | +- Automated linting and CI checks |
| 10 | +- Consistent documentation and release practices |
| 11 | +- Shared best practices across many pipelines |
| 12 | + |
| 13 | +## What this espanso package is for |
| 14 | + |
| 15 | +This package adds quick text expansions for frequent nf-core comments used in: |
| 16 | + |
| 17 | +- GitHub pull request reviews |
| 18 | +- GitHub issues |
| 19 | +- Slack support and collaboration |
| 20 | + |
| 21 | +The goal is to make repeated feedback faster, clearer, and more consistent. |
| 22 | + |
| 23 | +## Trigger discovery |
| 24 | + |
| 25 | +Most triggers in this package start with `:nfc-`. |
| 26 | + |
| 27 | +Type `:nfc-` in any text field where Espanso is active (for example GitHub or Slack) to see and use the nf-core shortcuts quickly. |
| 28 | + |
| 29 | +## Available triggers |
| 30 | + |
| 31 | +This package uses grouped triggers with selection popups. |
| 32 | +Most groups have one descriptive trigger, with aliases only where helpful. |
| 33 | + |
| 34 | +- `:nfc-lint` |
| 35 | + - Replacement: |
| 36 | + - You can run `nextflow lint -format -sort-declarations -spaces 4 -harshil-alignment` on this file to clean this up nicely. |
| 37 | +- `:nfc-modcore` |
| 38 | + - Possible replacements: |
| 39 | + - According to the module specifications we want the module name reflected in the process name. |
| 40 | + - Let the module user decide output naming via `ext-prefix` and use `${prefix}`. |
| 41 | + - Can you please add ontologies to the meta map? |
| 42 | + - Can we put all these inputs into one tuple? |
| 43 | + - If input and output names can overlap, use `task.ext.prefix` to disambiguate (example guard: `if ("${tsv}" == "${prefix}.tsv") ...`). |
| 44 | +- `:nfc-versions` |
| 45 | + - Possible replacements: |
| 46 | + - Versions expression snippet: |
| 47 | + - `process.out.findAll { key, val -> key.startsWith('versions') }` |
| 48 | + - Request to migrate versions output to topics. |
| 49 | +- `:nfc-snap` (alias: `:nfc-test`) |
| 50 | + - Possible replacements: |
| 51 | + - Use `snapshot(sanitizeOutput(process.out)).match()` for cleaner snapshots. |
| 52 | + - Ask to include more files in snapshots. |
| 53 | + - Use `snapshot(sanitizeOutput(process.out)).match()` for stub assertions. |
| 54 | + - Use `nft-bam` (including `.getReadsMD5()`) for BAM content assertions. |
| 55 | + - Use `nft-vcf` for VCF content assertions. |
| 56 | + - Insert a GitHub ````suggestion```` block with `snapshot(sanitizeOutput(process.out)).match()`. |
| 57 | + - Include `ext.args` in `main.nf.test`. |
| 58 | +- `:nfc-docker` |
| 59 | + - Possible replacements: |
| 60 | + - Encourage bringing tools to bioconda so docker/singularity containers can be built automatically. |
| 61 | + - Recommend uploading custom containers to nf-core quay.io and requesting via `#request-core`. |
| 62 | +- `:nfc-contrib` |
| 63 | + - Possible replacements: |
| 64 | + - Ask contributor to join the nf-core GitHub organization so CI can run. |
| 65 | + - Recommend one module per PR. |
| 66 | + - Ask to split a large PR into one PR per module/subworkflow. |
| 67 | +- `:nfc-thanks` |
| 68 | + - Possible replacements: |
| 69 | + - Thank-you note with mention of added review comments. |
| 70 | + - Thank-you note with guidance to module specs and examples in repository. |
| 71 | +- `:nfc-pipeline` (alias: `:nfc-info`) |
| 72 | + - Possible replacements: |
| 73 | + - Request `nextflow.log`, `samplesheet.csv`, and the exact run command. |
| 74 | + - Suggest using a custom configuration file (with docs reference). |
| 75 | +- `:prtodo` |
| 76 | + - Replacement: |
| 77 | + - `-commenter:@me -review:changes-requested` |
| 78 | +- `:nfc-github` (alias: `:nfc-gh`) |
| 79 | + - Possible replacements: |
| 80 | + - Recommend opening a new PR from the latest module template via `nf-core m create`. |
| 81 | + - Close due to inactivity message with reopen/new PR guidance. |
| 82 | + |
| 83 | +## Typical usage |
| 84 | + |
| 85 | +1. Type a configured trigger in GitHub or Slack. |
| 86 | +2. Let espanso expand it into the full comment. |
| 87 | +3. Adjust project-specific details before sending. |
| 88 | + |
| 89 | +## Notes |
| 90 | + |
| 91 | +- Keep expansions short, respectful, and actionable. |
| 92 | +- Prefer links to nf-core docs when suggesting standards. |
| 93 | +- Update triggers regularly as team conventions evolve. |
0 commit comments