From ee4c88f34802a18876f66b3c59fd9d18f8afef02 Mon Sep 17 00:00:00 2001
From: Bonnie Simon <49012815+bonniesimon@users.noreply.github.com>
Date: Wed, 14 Jan 2026 00:13:24 +0530
Subject: [PATCH 1/3] Update README with wildcard queue explanation

Clarify behavior of wildcard in queue configuration
---
 README.md | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/README.md b/README.md
index cee99f85..609d9b4d 100644
--- a/README.md
+++ b/README.md
@@ -340,6 +340,19 @@ instead of this:
 queues: back*
 ```
 
+Also, if a wildcard (*) is included alongside explicit queue names, Solid Queue treats the configuration as queues: *.
+
+This means that when * appears alongside explicit queue names, the worker uses the unfiltered polling query, ignores the specified queue order, and processes jobs from all queues.
+
+For example, this:
+```yml
+queues: [default, backend, incineration, *]
+```
+
+behaves the same as:
+```yml
+queues: *
+```
 
 ### Threads, processes, and signals
 

From 75972b5ad30cd4936f8781fd555f4d19ef979318 Mon Sep 17 00:00:00 2001
From: Bonnie Simon <49012815+bonniesimon@users.noreply.github.com>
Date: Thu, 15 Jan 2026 00:34:11 +0530
Subject: [PATCH 2/3] Update README with wildcard queue behavior details

Clarify behavior of wildcards in queue configuration
---
 README.md | 16 ++--------------
 1 file changed, 2 insertions(+), 14 deletions(-)

diff --git a/README.md b/README.md
index 609d9b4d..4afbd01c 100644
--- a/README.md
+++ b/README.md
@@ -258,6 +258,8 @@ Here's an overview of the different options:
   ```
 
   This will create a worker fetching jobs from all queues starting with `staging`. The wildcard `*` is only allowed on its own or at the end of a queue name; you can't specify queue names such as `*_some_queue`. These will be ignored.
+  
+  Also, if a wildcard (*) is included alongside explicit queue names, for example: `queues: [default, backend, *]`, then it would behave like `queues: *`
 
   Finally, you can combine prefixes with exact names, like `[ staging*, background ]`, and the behaviour with respect to order will be the same as with only exact names.
 
@@ -340,20 +342,6 @@ instead of this:
 queues: back*
 ```
 
-Also, if a wildcard (*) is included alongside explicit queue names, Solid Queue treats the configuration as queues: *.
-
-This means that when * appears alongside explicit queue names, the worker uses the unfiltered polling query, ignores the specified queue order, and processes jobs from all queues.
-
-For example, this:
-```yml
-queues: [default, backend, incineration, *]
-```
-
-behaves the same as:
-```yml
-queues: *
-```
-
 ### Threads, processes, and signals
 
 Workers in Solid Queue use a thread pool to run work in multiple threads, configurable via the `threads` parameter above. Besides this, parallelism can be achieved via multiple processes on one machine (configurable via different workers or the `processes` parameter above) or by horizontal scaling.

From 9bf105ca54661973cb311bc295fc3d87233bca50 Mon Sep 17 00:00:00 2001
From: Bonnie Simon <49012815+bonniesimon@users.noreply.github.com>
Date: Thu, 15 Jan 2026 00:36:59 +0530
Subject: [PATCH 3/3] Remove extra formating

Add a blank line for better readability in README.
---
 README.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/README.md b/README.md
index 4afbd01c..b49f9c60 100644
--- a/README.md
+++ b/README.md
@@ -342,6 +342,7 @@ instead of this:
 queues: back*
 ```
 
+
 ### Threads, processes, and signals
 
 Workers in Solid Queue use a thread pool to run work in multiple threads, configurable via the `threads` parameter above. Besides this, parallelism can be achieved via multiple processes on one machine (configurable via different workers or the `processes` parameter above) or by horizontal scaling.