From 11c2e2e95bffaa04e65c8c6a03b079c4351f9d62 Mon Sep 17 00:00:00 2001
From: alisboav <marta.vila.fernandes@cern.ch>
Date: Aug 21 2023 10:51:23 +0000
Subject: Example of how to enable a module via mock.module_setup_commands


---

diff --git a/docs/source/using_the_koji_build_system.rst b/docs/source/using_the_koji_build_system.rst
index b6b43d1..c46815b 100644
--- a/docs/source/using_the_koji_build_system.rst
+++ b/docs/source/using_the_koji_build_system.rst
@@ -433,6 +433,13 @@ environment follows:
 * ``mock.module_setup_commands`` - commands for configuring the modules active
   in a buildroot. Available in `mock 2.4
   <https://github.com/rpm-software-management/mock/wiki/Release-Notes-2.4>`__.
+    - Example of how to enable a module:
+    
+    ::
+
+      koji edit-tag dnf-fedora-tag -x mock.module_setup_commands='[["enable", "<module_name>"]]'
+
+
 * ``mock.forcearch`` - 0/1 value. If true mock will set the ``forcearch``
   config option to match the target arch of each buildroot.
 * ``mock.yum.best`` - 0/1 value. If set yum/dnf will use highest available rpm