5d09bd4b93
## Introduction
Unless I'm mistaken neither the `inputs.type` or `inputs.type` syntax
exists for `composite actions`.
By default it seems like any `Composite action` inputs are considered as
`string`.
```yml
name: Nx Affected CI
inputs:
parallel:
required: false
types: [number]
default: 3
tag:
required: false
types: [string]
tasks:
required: true
types: [string]
```
## Suggestion
To avoid misunderstanding of our composite actions inputs signature I
would recommend removing any `type` props but also default any inputs as
`strings`
## Misc
- Please find related GitHub community discussion
https://github.com/orgs/community/discussions/65588
18 lines
440 B
YAML
18 lines
440 B
YAML
name: Nx Affected CI
|
|
inputs:
|
|
parallel:
|
|
required: false
|
|
default: '3'
|
|
tag:
|
|
required: false
|
|
tasks:
|
|
required: true
|
|
|
|
runs:
|
|
using: "composite"
|
|
steps:
|
|
- name: Get last successful commit
|
|
uses: nrwl/nx-set-shas@v4
|
|
- name: Run affected command
|
|
shell: bash
|
|
run: npx nx affected --nxBail --configuration=ci -t=${{ inputs.tasks }} --parallel=${{ inputs.parallel }} --exclude='*,!tag:${{ inputs.tag }}' |