actions-marketplace-validations/Issue Forms Dropdown Options
Populates options for a version dropdown issue forms element
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| github_token | Github token | — | ${{ github.token }} |
| template | The location of the template file used to build the form, useful for ease of maintenance. Dynamic dropdowns will persist between action runs. Static dropdowns (dropdowns with populated options) take precedence over their built counterpart, meaning that you should not edit the built form ever, see https://github.com/ShaMan123/gha-form-dropdown-options/pull/2/commits/7cbd904caccb60c9bf52f066d11b303e439fe598. This behavior makes sense but could have been handled with ease if flagging dynamic dropdowns in forms was possible. It might change to a stricter approach in the future using id prefixing. It is suggested using the template option once in the first step updating the form and omitting it afterwards. | — | — |
| form | The location of the yaml form file | yes | — |
| dropdown | The id of the dropdown in the yaml form to populate options into Prefix the id with the value of `id_prefix`, see `strategy` for more details | yes | — |
| options | A stringified array of options Supports the dynamic substitution templates: `{...}`, `{{...}}` | yes | — |
| label | The label of the dropdown Supports the dynamic substitution templates: `{...}`, `{{...}}` | — | — |
| description | The description of the dropdown Supports the dynamic substitution templates: `{...}`, `{{...}}` | — | — |
| unique | Whether `options` should be unique | — | true |
| commit_message | defaults to `chore(): update [REPORT_NAME]` | — | — |
| strategy | The strategy used to determine if a dropdown is static or not. The `empty-options` strategy determines if a dropdown is dynamic by checking if the template's options are empty. The `id-prefix` strategy determines if a dropdown is dynamic or not by checking its id prefix depending on the value of `id_prefix`. `id-prefix` is strict and allows more flexibility, such as dynamic substitution. The `mixed` strategy uses both. | — | mixed |
| id_prefix | The prefix used by `strategy` to determine if a dropdown is dynamic | — | _ |
| dry_run | Pass `no-write` to leave `form` untouched Pass `no-commit` to leave the git history untouched Pass `no-push` to leave the commit untouched | — | — |
| pull_strategy | The git pull strategy to use before pushing changes. Use `ff-only` for fast-forward only (default), or `rebase` to rebase local changes. | — | ff-only |
Outputs
| name | description |
|---|---|
| form | JSON stringified form |
| modified | form has been modified by action |
| pushed | pushed to origin |