You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: documentation/docs/features/automations.md
+15-1Lines changed: 15 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -132,7 +132,21 @@ The State field matches these status buckets:
132
132
133
133
### Regex Support
134
134
135
-
Full RE2 (Go regex) syntax supported. Patterns are case-insensitive by default. The UI validates patterns and shows helpful error messages for invalid regex.
135
+
Full RE2 (Go regex) syntax supported. Patterns are case-insensitive by default.
136
+
137
+
Regex can be used either by selecting **matches regex** or by enabling the **Regex** toggle for a condition:
138
+
139
+
- When regex is enabled, the condition checks whether the regex matches the field value.
140
+
-`not equals` and `not contains` invert the regex result (true only if the regex does **not** match).
141
+
- Operators like `equals`, `contains`, `starts with`, and `ends with` are treated as regex match when regex is enabled.
142
+
- Regex is not implicitly anchored: use `^` and `$` if you want an exact/full-string match (example: `^BHD$`).
143
+
144
+
Field notes:
145
+
146
+
-**Tracker**: checked against multiple candidates (raw URL, extracted domain, and optional customization display name). Negative regex passes only if **none** of the candidates match.
147
+
-**Tags**: without regex, string operators are applied per-tag. With regex enabled, the regex is matched against the full raw tags string.
148
+
149
+
The UI validates patterns and shows helpful error messages for invalid regex.
0 commit comments