Skip to content

bug: action not working when CONFIG is specified #154

@justinmchase

Description

@justinmchase

Bug Report

When using the action, if you don't specify the config it seems to not apply any of the hooks.

Commit or Tag Version

2.0.2

Expected Behaviour

All of the hooks are processed as normal and the file provided is used.

Actual Behaviour

The VERSION is incremented but none of the files in the version.yml config are updated.

Steps to Reproduce

- uses: optum/semver-cli@2.0.0    
  with:
    command: inc
    sub-command: none
    prerelease: ${{ format('pr.{0}', github.run_number) }}
    build: ${{ github.run_attempt }}

Further comments

It seems like there is an issue with applying the inputs from env vars, I think we should just pass the input values right in and then do the flag conditionals in bash.

Metadata

Metadata

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions