From 8248ad0261b3cdf741f5f61f8e940a94c8125770 Mon Sep 17 00:00:00 2001 From: "patchback[bot]" <45432694+patchback[bot]@users.noreply.github.com> Date: Tue, 10 Dec 2024 10:41:22 -0500 Subject: [PATCH] fix file name to execution-environment.yml (#2240) (#2279) * fix file name to execution-environment.yml * fix syntax (cherry picked from commit 22a4625c42d6953daa386511cd63d0b6338142ad) Co-authored-by: Akira Yokochi --- .../rst/dev_guide/developing_collections_structure.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/docsite/rst/dev_guide/developing_collections_structure.rst b/docs/docsite/rst/dev_guide/developing_collections_structure.rst index 7135c22f36..a1fef6ea2c 100644 --- a/docs/docsite/rst/dev_guide/developing_collections_structure.rst +++ b/docs/docsite/rst/dev_guide/developing_collections_structure.rst @@ -286,8 +286,8 @@ A collection can store some additional metadata in a ``runtime.yml`` file in the - my_module - another.collection.another_module -execution_environments.yml -^^^^^^^^^^^^^^^^^^^^^^^^^^ +execution-environment.yml +^^^^^^^^^^^^^^^^^^^^^^^^^ If your collection has requirements, you can specify them in the ``execution-environment.yml`` file in the ``meta`` directory. This ensures users do not need to add these requirements manually when building :ref:`Execution Environments` containing your collection.