Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Support "multi-choice" input type for manual workflows

See original GitHub issue

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

Issue Analytics

State:
Created a year ago
Reactions:285
Comments:108 (1 by maintainers)

Top GitHub Comments

14reactions

nikola-jokiccommented, May 17, 2023

Hey everyone, this is not really a runner issue ☺️. We have communicated this issue to the correct team, but I will leave it open because it gained so much attention ☺️

7reactions

pritom007commented, May 3, 2023

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

Also it would be nice to have a option to take user inputs as one of the multi-choice.

on:
  workflow_dispatch:
    inputs:
      name:
        type: multi-choice
        description: select packages
        options: 
        - go-service1
        - go-service2
        - py-service1
        - input()