Add conda-lock to example

.github/workflows/update-readme.yml

@@ -11,21 +11,22 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Check out repository
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
         with:
           persist-credentials: false
           fetch-depth: 0
 
       - name: Set up Python
-        uses: actions/setup-python@v3
+        uses: actions/setup-python@v5
         with:
           python-version: '3.x'
+          cache: 'pip'
 
       - name: Install Python dependencies
         run: |
           python -m pip install --upgrade pip
           pip install markdown-code-runner
-          pip install -e .
+          pip install -e ".[conda-lock]" setuptools
 
       - name: Run markdown-code-runner
         run: |

README.md

@@ -413,7 +413,7 @@ See `unidep conda -h` for more information:
 <!-- ⚠️ This content is auto-generated by `markdown-code-runner`. -->
 ```bash
 usage: unidep conda-lock [-h] [--only-global] [--check-input-hash]
-                         [-d DIRECTORY] [-v]
+                         [--skip-global] [-d DIRECTORY] [-v]
                          [--platform {linux-64,linux-aarch64,linux-ppc64le,osx-64,osx-arm64,win-64}]
                          [--depth DEPTH]
 
@@ -432,6 +432,9 @@ options:
   --check-input-hash    Check existing input hashes in lockfiles before
                         regenerating lock files. This flag is directly passed
                         to `conda-lock`.
+  --skip-global         Skip the call to `conda-lock`, only regenerate the sub
+                        `conda-lock.yml` files. Requires the global `conda-
+                        lock.yml` file to already exist.
   -d DIRECTORY, --directory DIRECTORY
                         Base directory to scan for `requirements.yaml`
                         file(s), by default `.`

example/README.md

@@ -8,6 +8,7 @@
 - [Combine one or multiple `requirements.yaml` files into a single `environment.yaml` file](#combine-one-or-multiple-requirementsyaml-files-into-a-single-environmentyaml-file)
 - [Install a `requirements.yaml` file directly with `pip`](#install-a-requirementsyaml-file-directly-with-pip)
 - [Install a `requirements.yaml` file directly with `unidep`](#install-a-requirementsyaml-file-directly-with-unidep)
+- [Create a global `conda-lock.yml` and per project `conda-lock.yml` files](#create-a-global-conda-lockyml-and-per-project-conda-lockyml-files)
 
 <!-- END doctoc generated TOC please keep comment here to allow auto update -->
 
@@ -81,3 +82,27 @@ Just run `unidep install ./project1` or `unidep install -e ./project1` for an ed
 ```
 
 <!-- OUTPUT:END -->
+
+## Create a global `conda-lock.yml` and per project `conda-lock.yml` files
+
+Using `unidep conda-lock` we can create a global `conda-lock.yml` file and per project `conda-lock.yml` files that are consistent with the global lock file.
+
+<!-- CODE:BASH:START -->
+<!-- echo '```bash' -->
+<!-- unidep conda-lock --check-input-hash -->
+<!-- echo '```' -->
+<!-- CODE:END -->
+<!-- OUTPUT:START -->
+<!-- ⚠️ This content is auto-generated by `markdown-code-runner`. -->
+```bash
+✅ Generated environment file at `tmp.environment.yaml` from `project1/requirements.yaml`, `project2/requirements.yaml`, `project3/requirements.yaml`
+🔒 Locking dependencies with `conda-lock lock --file tmp.environment.yaml --lockfile conda-lock.yml --check-input-hash`
+
+✅ Global dependencies locked successfully in `conda-lock.yml`.
+📝 Generated lock file for `project1/requirements.yaml`: `project1/conda-lock.yml`
+📝 Generated lock file for `project2/requirements.yaml`: `project2/conda-lock.yml`
+📝 Generated lock file for `project3/requirements.yaml`: `project3/conda-lock.yml`
+✅ Analyzed all lock files and found no inconsistencies.
+```
+
+<!-- OUTPUT:END -->