From b4f103c5a97126dfdf3e426ca77d91567b541d9b Mon Sep 17 00:00:00 2001
From: mashehu <mashehu3@gmail.com>
Date: Fri, 28 Apr 2023 13:24:39 +0200
Subject: [PATCH] update subworkflow commands for rich-codex

---
 README.md | 8 ++------
 1 file changed, 2 insertions(+), 6 deletions(-)

diff --git a/README.md b/README.md
index b3b62beaf0..0de42e86e8 100644
--- a/README.md
+++ b/README.md
@@ -1183,11 +1183,9 @@ To help developers build new subworkflows, the `nf-core subworkflows create-test
 After you have written a minimal Nextflow script to test your subworkflow in `/tests/subworkflow/<subworkflow_name>/main.nf`, this command will run the tests for you and create the `/tests/subworkflow/<tool>/<subtool>/test.yml` file.
 
 <!-- RICH-CODEX
-working_dir: tmp/subworkflows
+working_dir: tmp/modules
 extra_env:
   PROFILE: 'conda'
-before_command: >
-  echo "repository_type: modules" >> .nf-core.yml
 -->
 
 ![`nf-core subworkflows create-test-yml bam_stats_samtools --no-prompts --force`](docs/images/nf-core-subworkflows-create-test.svg)
@@ -1199,12 +1197,10 @@ To run unit tests of a subworkflow that you have installed or the test created b
 You can specify the subworkflow name in the form TOOL/SUBTOOL in command line or provide it later by prompts.
 
 <!-- RICH-CODEX
-working_dir: tmp/subworkflows
+working_dir: tmp/modules
 timeout: 30
 extra_env:
   PROFILE: 'conda'
-before_command: >
-  echo "repository_type: pipeline" >> .nf-core.yml
 -->
 
 ![`nf-core subworkflows test bam_rseqc --no-prompts`](docs/images/nf-core-subworkflows-test.svg)