Update broke args

[budimanjojo]

Hello, after updating I can't get it to work with args anymore.
Here's what in my current action file:

jobs:
  lint:
    runs-on: ubuntu-latest
    steps:
    - name: Lint Ansible
      uses: ansible/ansible-lint-action@main
      with:
      args: "-c ./.github/.ansible-lint"

It was working before update (I used to have targets and override-deps too).
Here's the error log:

Run ansible/ansible-lint-action@main
  with:
    args: -c ./.github/.ansible-lint
/usr/bin/docker run --name quayioansiblecreatoreev041_8966ad --label 372a9e --workdir /github/workspace --rm -e INPUT_ARGS -e GITHUB_ACTIONS -e GITHUB_WORKFLOW -e HOME -e GITHUB_JOB -e GITHUB_REF -e GITHUB_SHA -e GITHUB_REPOSITORY -e GITHUB_REPOSITORY_OWNER -e GITHUB_RUN_ID -e GITHUB_RUN_NUMBER -e GITHUB_RETENTION_DAYS -e GITHUB_RUN_ATTEMPT -e GITHUB_ACTOR -e GITHUB_HEAD_REF -e GITHUB_BASE_REF -e GITHUB_EVENT_NAME -e GITHUB_SERVER_URL -e GITHUB_API_URL -e GITHUB_GRAPHQL_URL -e GITHUB_REF_NAME -e GITHUB_REF_PROTECTED -e GITHUB_REF_TYPE -e GITHUB_WORKSPACE -e GITHUB_ACTION -e GITHUB_EVENT_PATH -e GITHUB_ACTION_REPOSITORY -e GITHUB_ACTION_REF -e GITHUB_PATH -e GITHUB_ENV -e GITHUB_STEP_SUMMARY -e RUNNER_OS -e RUNNER_ARCH -e RUNNER_NAME -e RUNNER_TOOL_CACHE -e RUNNER_TEMP -e RUNNER_WORKSPACE -e ACTIONS_RUNTIME_URL -e ACTIONS_RUNTIME_TOKEN -e ACTIONS_CACHE_URL -e GITHUB_ACTIONS=true -e CI=true --entrypoint "/usr/local/bin/ansible-lint" -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/_temp/_runner_file_commands":"/github/file_commands" -v "/home/runner/work/ansible-role-duossh/ansible-role-duossh":"/github/workspace" quay.io/ansible/creator-ee:v0.4.1  "-vvv" "-c ./.github/.ansible-lint"
WARNING: PATH altered to include /usr/bin
Config file not found '/github/workspace/ ./.github/.ansible-lint'

The config file is in my .github/.ansible-lint, I don't know why there is a space after /github/workspace.

[officel]

see #87

We have the same problem.