Skip to content

Update README with wildcard queue explanation #704

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rosa merged 3 commits into from
Jan 14, 2026
Merged

Update README with wildcard queue explanation #704

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ee4c88f
Update README with wildcard queue explanation
bonniesimon Jan 13, 2026
75972b5
Update README with wildcard queue behavior details
bonniesimon Jan 14, 2026
9bf105c
Remove extra formating
bonniesimon Jan 14, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
Loading