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
+16Lines changed: 16 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -201,6 +201,22 @@ See the workflows:
201
201
202
202
</details>
203
203
204
+
## workflow_input.yml
205
+
206
+
<details>
207
+
208
+
<summary>Adjust how a workflow will run with custom input.</summary>
209
+
210
+
<br/>When using the `workflow_dispatch` event, you can optionally specify inputs that are passed to the workflow.
211
+
212
+
This trigger only receives events when the workflow file is on the default branch. This means you have to merge your changes to `main` or `master` before you can test your inputs. It would be wise to try input changes in a totally separate workflow before merging them into critical workflows.
213
+
214
+
Also, if the event that triggers the workflow isn't `workflow_dispatch` the input values are empty/null. This is true even if you have default values defined.
215
+
216
+
See the [workflow](.github/workflows/workflow_input.yml).
0 commit comments