Proper types for all inputs
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 bug
Proper types for all inputs.
Different inputs contexts have different sets of supported types.
Lack of array or object types.
Impairs workflow composability, maintainability, and security.
To Reproduce
workflow_call supports type with boolean, number, or string
workflow_dispatch supports type with boolean, choice, number, or string
Action inputs: no types at all
https://blog.yossarian.net/2023/09/22/GitHub-Actions-could-be-so-much-better#:~:text=Real%20types%20would%20be%20nice
Expected behavior
Same set of supported types for all inputs contexts.
Add array and object types.
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
Compare the input behavior of workflow_call, workflow_dispatch, and action inputs described in the issue. Determine how to support a consistent set of types, including arrays and objects; done means the supported types are aligned across all three input contexts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100