From ac1ca40fb3ed0a0fce387ae70cb8937208a13e03 Mon Sep 17 00:00:00 2001 From: Matt Martz Date: Wed, 17 Aug 2022 15:10:00 -0500 Subject: [PATCH] Fix incorrect docs about how to enable manifest functionality (#78572) --- .../rst/dev_guide/developing_collections_distributing.rst | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/docsite/rst/dev_guide/developing_collections_distributing.rst b/docs/docsite/rst/dev_guide/developing_collections_distributing.rst index 57774ec3c25..2fe232d2b9a 100644 --- a/docs/docsite/rst/dev_guide/developing_collections_distributing.rst +++ b/docs/docsite/rst/dev_guide/developing_collections_distributing.rst @@ -250,7 +250,12 @@ By default, the ``MANIFEST.in`` style directives would exclude all files by defa The ``manifest.directives`` supplied in :file:`galaxy.yml` are inserted after the default includes and before the default excludes. -To enable the use of manifest directives without supplying your own, insert either ``manifest: {}`` or ``manifest: null`` in the :file:`galaxy.yml` file and remove any use of ``build_ignore``. +To enable the use of manifest directives without supplying your own, set ``manifest.directives`` to either ``[]`` or ``null`` in the :file:`galaxy.yml` file and remove any use of ``build_ignore``: + +.. code-block:: yaml + + manifest: + directives: [] If the default manifest directives do not meet your needs, you can set ``manifest.omit_default_directives`` to a value of ``true`` in :file:`galaxy.yml`. You then must specify a full compliment of manifest directives in :file:`galaxy.yml`. The defaults documented above are a good starting point.