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: docs/releases.md
+12-6Lines changed: 12 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -110,12 +110,20 @@ There are two ways to create a patch pull request:
110
110
111
111
After a pull request containing the fix has been merged, a maintainer can add a comment on that same PR with the following format:
112
112
113
-
`/patch <channel> [--dry-run]`
113
+
`/patch [channel]`
114
114
115
-
-**channel**: `stable` or `preview`
116
-
-**--dry-run** (optional): If included, the workflow will run in dry-run mode. This will create the PR with "[DRY RUN]" in the title, and merging it will trigger a dry run of the final release, so nothing is actually published.
115
+
-**channel** (optional):
116
+
-_no channel_ - patches both stable and preview channels (default, recommended for most fixes)
117
+
-`both` - patches both stable and preview channels (same as default)
118
+
-`stable` - patches only the stable channel
119
+
-`preview` - patches only the preview channel
117
120
118
-
Example: `/patch stable --dry-run`
121
+
Examples:
122
+
123
+
-`/patch` (patches both stable and preview - default)
124
+
-`/patch both` (patches both stable and preview - explicit)
125
+
-`/patch stable` (patches only stable)
126
+
-`/patch preview` (patches only preview)
119
127
120
128
The `Release: Patch from Comment` workflow will automatically find the merge commit SHA and trigger the `Release: Patch (1) Create PR` workflow. If the PR is not yet merged, it will post a comment indicating the failure.
121
129
@@ -134,8 +142,6 @@ This workflow will automatically:
134
142
4. Cherry-pick your specified commit into the hotfix branch.
135
143
5. Create a pull request from the hotfix branch back to the release branch.
136
144
137
-
**Important:** If you select `stable`, the workflow will run twice, creating one PR for the `stable` channel and a second PR for the `preview` channel.
138
-
139
145
#### 2. Review and Merge
140
146
141
147
Review the automatically created pull request(s) to ensure the cherry-pick was successful and the changes are correct. Once approved, merge the pull request.
0 commit comments