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
|`--name`|`sync`, `complete`, `update`| Custom release name. For `sync`, the value is applied to the targeted release — both newly created releases and existing ones get the provided name. For `complete` and `update`, sets the name on the targeted release. |
155
-
|`--release-version`|`sync`, `complete`, `update`| Release version identifier. For `sync`, defaults to short commit hash. For `complete` and `update`, selects an existing release with that version (errors if none exists); does not change a release's version. If omitted, targets the most recent started release. |
156
-
|`--stage`|`update`| Target deployment stage (required for `update`) |
157
-
|`--include-paths`|`sync`| Filter commits by changed file paths |
158
-
|`--json`|`sync`, `complete`, `update`| Output result as JSON on stdout. Logs are emitted as JSON Lines (one object per line) on stderr. |
159
-
|`--quiet`|`sync`, `complete`, `update`| Suppress info-level output. Warnings and errors are still printed. |
160
-
|`--verbose`|`sync`, `complete`, `update`| Print detailed progress including debug diagnostics |
161
-
|`--timeout`|`sync`, `complete`, `update`| Max duration in seconds before aborting (default: 60) |
|`--name`|`sync`, `complete`, `update`| Custom release name. For `sync`, the value is applied to the targeted release — both newly created releases and existing ones get the provided name. For `complete` and `update`, sets the name on the targeted release. |
155
+
|`--release-version`|`sync`, `complete`, `update`| Release version identifier. For `sync`, defaults to short commit hash. For `complete` and `update`, selects an existing release with that version (errors if none exists); does not change a release's version. If omitted, targets the most recent started release. |
156
+
|`--stage`|`update`| Target deployment stage (required for `update`) |
157
+
|`--include-paths`|`sync`| Filter commits by changed file paths |
|`--json`|`sync`, `complete`, `update`| Output result as JSON on stdout. Logs are emitted as JSON Lines (one object per line) on stderr. |
160
+
|`--quiet`|`sync`, `complete`, `update`| Suppress info-level output. Warnings and errors are still printed. |
161
+
|`--verbose`|`sync`, `complete`, `update`| Print detailed progress including debug diagnostics |
162
+
|`--timeout`|`sync`, `complete`, `update`| Max duration in seconds before aborting (default: 60) |
162
163
163
164
### Command Targeting
164
165
@@ -209,6 +210,22 @@ Patterns use [Git pathspec](https://git-scm.com/docs/gitglossary#Documentation/g
209
210
210
211
Path patterns can also be configured in your pipeline settings in Linear. If both are set, the CLI `--include-paths` option takes precedence.
211
212
213
+
### Commit Message Filtering
214
+
215
+
Use `--include-messages` to only scan commits whose subject (first line) matches a regular expression. Useful when the default commit range pulls in noise — direct pushes without issue links, bot commits, or merge commits you don't want appearing in releases.
216
+
217
+
```bash
218
+
# Only commits that mention a Linear issue identifier in the subject
The regex is matched against the commit subject only (everything before the first newline) — body lines such as squash dumps or co-author trailers are ignored. Use the regex's own `|` alternation to combine multiple patterns; remember to escape regex metacharacters in shell strings.
226
+
227
+
`--include-messages` composes with `--include-paths`: a commit must pass both filters to be scanned.
228
+
212
229
## How It Works
213
230
214
231
1.**Fetches the latest release** from your Linear pipeline to determine the commit range
0 commit comments