From b87021def7f45b27fad1b2c982c9e44cb2e6c96c Mon Sep 17 00:00:00 2001
From: Felix K <17876666+fkirc@users.noreply.github.com>
Date: Sun, 10 Dec 2023 18:37:14 +0100
Subject: [PATCH] Update README.md

---
 README.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/README.md b/README.md
index be42df3..e5a2a52 100644
--- a/README.md
+++ b/README.md
@@ -297,6 +297,10 @@ jobs:
 
 ### Example 3: Skip using `paths_filter`
 
+> [!WARNING]  
+> If the paths_filter option is not working correctly, then you could copy the “example 1" multiple times according to your needs (see #326 for details).
+
+
 The `paths_filter` option can be used if you have multiple jobs in a workflow and want to skip them based on different [`paths_ignore`](#paths_ignore) / [`paths`](#paths) patterns. When defining such filters, the action returns corresponding information in the [`paths_result`](#paths_result) output.
 For example in a monorepo, you might want to run jobs related to the "frontend" only if some files in the corresponding "frontend/" folder have changed and the same for "backend". This can be achieved with the following configuration: