Support "multi-choice" input type for manual workflows
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.3k
- Forks
- 1.4k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 24
Description
Describe the enhancement
Current set of input types doesn't cover some use-cases for manual workflows
We use a single gh-action as an entrypoint of deploying packages from our monorepo, and sometimes we need to manually deploy several packages simultaneously. Up until now we just went with a set of Booleans, so we could tick all the packages we needed to run our CI/CD against via UI. However, we speedily reached a limit of 10 input values
Introducing an input type that would store a, say, json array could help:
on:
workflow_dispatch:
inputs:
name:
type: multi-choice
description: select packages
options:
- go-service1
- go-service2
- py-service1
...and in fact would be more logical with less copy-paste overhead for our use-case
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue centers on workflow_dispatch inputs in GitHub Actions; start by tracing how the runner handles manual workflow inputs and review the discussion for established semantics. Done means a supported multi-choice input with a defined representation, such as the proposed JSON array, and documented behavior, but the issue does not identify files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, github-actions
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100