Unable to use working-directory with docker based actions

I have a couple actions that need to be run from a specific folder in the repo. If I set the working-directory value of a script based action that works as expected, but setting it for a step that uses a docker based action results in an error.

### ERRORED 21:14:14Z

- Your workflow file was invalid: The pipeline is not valid. .github/workflows/build_frontend.yml (Line: 34, Col: 9): Unexpected value 'working-directory'

There’s no mention in the docs if this is only usable in specific scearios. https://help.github.com/en/articles/workflow-syntax-for-github-actions#jobsjob_idstepsworking-directory

Are there any plants to allow this to work with docker based actions? It would allow me to remove the custom code I had to add to a number of my actions that mimicks the working-directory setting.

Could you share the snippet of your YAML that’s causing problems?

on: push

name: Build Frontend

    name: Build Frontend

    runs-on: ubuntu-latest

      - name: Checkout Repo
        uses: actions/checkout@master

      - name: Setup Node
        uses: actions/setup-node@v1.1.2
          node-version: "12.x"

      - name: Version Info
        run: |
          node --version
          npm --version

      - name: Install Frontend Dependencies
        run: npm ci
        working-directory: src/website

      - name: Build CSS
        run: npm run css
        working-directory: src/website

      - name: Stylelint
        uses: xt0rted/stylelint-action@c7b560bfa8d157a17d820dcd30b02bbee745a920
        working-directory: src/website
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          args: scss/frameworks/ **/*.scss scss/app/** /*.scss

The new workflow editor says that working-directory can’t be used with uses & with. So I guess this is by design right now. The docs don’t mention it though which is why it felt like a bug.