From ad550d045ac7bc22852d5428bdc8f36bff89e6d2 Mon Sep 17 00:00:00 2001
From: 6543 <6543@obermui.de>
Date: Tue, 1 Oct 2024 22:45:13 +0100
Subject: [PATCH] address suggestion

---
 docs/docs/20-usage/40-secrets.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/docs/docs/20-usage/40-secrets.md b/docs/docs/20-usage/40-secrets.md
index e477a54e5..9b25b57da 100644
--- a/docs/docs/20-usage/40-secrets.md
+++ b/docs/docs/20-usage/40-secrets.md
@@ -48,6 +48,7 @@ This way, the secret key and environment variable name can differ.
 ### Using secrets in plugins-steps via "settings:"
 
 The `from_secret` syntax also work for settings in any hierarchy.
+Note that you can not use `secrets` and also not use it with `environment`, as this could alter the execution of plugins and so it is forbidden by the linter now.
 
 In the below example, the secret `SURGE_TOKEN` would be passed to the setting named `surge_token`, which again will be available in the plugin as environment variable named `PLUGIN_SURGE_TOKEN` (See [plugins](./51-plugins/20-creating-plugins.md#settings) for details).