From 16570d574653b336c5e3f99b43f33942fd72de2c Mon Sep 17 00:00:00 2001 From: Pierre-Yves Chibon Date: Dec 04 2020 08:44:54 +0000 Subject: Move the PAGURE_PLUGINS_CONFIG configuration key to a better place Signed-off-by: Pierre-Yves Chibon --- diff --git a/doc/configuration.rst b/doc/configuration.rst index 9538f71..133a8be 100644 --- a/doc/configuration.rst +++ b/doc/configuration.rst @@ -1909,8 +1909,16 @@ existing git tags via the API. When set to ``False``, this essentially makes the API ignore whether the ``force`` argument is set or not. +Defaults to: ``True`` + + +PAGURE_PLUGINS_CONFIG +~~~~~~~~~~~~~~~~~~~~~~ + +This option can be used to specify the configuration file used for loading +plugins. It is not set by default, instead if must be declared explicitly. +Also see the documentation on plugins at :ref:`plugins`. -Default to: ``True`` GIT_DEFAULT_BRANCH ~~~~~~~~~~~~~~~~~~ @@ -2069,6 +2077,7 @@ SSH_COMMAND_NON_REPOSPANNER The command to run if a repository is not on repospanner when aclchecker is in use. + MQTT Options ------------ @@ -2189,13 +2198,6 @@ notifications on commits made on all projects in a pagure instance. Defaults to: ``False``. -PAGURE_PLUGINS_CONFIG -~~~~~~~~~~~~~~~~~~~~~~ - -This option can be used to specify the configuration file used for loading -plugins. It is not set by default, instead if must be declared explicitly. -Also see the documentation on plugins at :ref:`plugins`. - Deprecated configuration keys -----------------------------