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: README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -236,9 +236,9 @@ Trigger:
236
236
Inputs:
237
237
238
238
-`run_on_issues`: remove the label from matching issues
239
-
-`closed_only`: when `run_on_issues` is enabled, only target closed issues
239
+
-`target_only_closed_issues`: when `run_on_issues` is enabled, only target closed issues
240
240
-`run_on_pull_requests`: remove the label from matching pull requests
241
-
-`merged_only`: when `run_on_pull_requests` is enabled, only target merged pull requests
241
+
-`target_only_closed_pull_requests`: when `run_on_pull_requests` is enabled, only target closed pull requests
242
242
-`label_name`: exact label name to remove
243
243
244
244
What it does:
@@ -252,7 +252,7 @@ What it does:
252
252
253
253
Notes:
254
254
255
-
- GitHub Actions does not currently support conditionally hiding or nesting `workflow_dispatch` inputs, so `closed_only` and `merged_only` can be described as dependent toggles but not visually tucked under their parent checkboxes.
255
+
- GitHub Actions does not currently support conditionally hiding or nesting `workflow_dispatch` inputs, so the closed-only toggles can be described as dependent but not visually tucked under their parent checkboxes.
0 commit comments