Explain what this does better than the native syntax?

[jorhett]

It's hard to grasp why this action exists, as this feature set is built into Actions today. If this provides a value not provided by GitHub Actions syntax you should add it to the documentation.

The documentation's example runs exactly the same, and much faster, written as the following:

jobs:
  something:
    name: Do something...
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
    
      - id: post-run-command
        needs: non-existent-command
        if: ${{ always() }}
        run: echo "this thing works!"

      - id: another-post-run-command
        needs: non-existent-command
        if: ${{ always() }}
        run: echo "this thing works again!"
        working-directory: not-required-but-you-can-provide-it

      - id: non-existent-command
        name: 'Running an non-existing command will fail...'
        run: run something that does not exist;

[ftzm]

Is this valid? I don't believe it's possible to specify "needs" on individual steps. I can find no documentation for it, and it doesn't work when I try it. Maybe I'm missing something.

[Piedone]

It doesn't work, You need to execute post-job code in a JavasScript action with runs.post.

[swissbuechi]

@jorhett
Your solution does not work for me.
I acctually needed the following syntax to make the post step always run (even if some steps above fail):

    - name: Show VPN log
      uses: webiny/[email protected]
      if: always()
      with:
        run: sudo cat vpn.log

Thanks to @adrians5j for publishing this action!

[swissbuechi]

It's hard to grasp why this action exists, as this feature set is built into Actions today. If this provides a value not provided by GitHub Actions syntax you should add it to the documentation.

The documentation's example runs exactly the same, and much faster, written as the following:

jobs:
  something:
    name: Do something...
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
    
      - id: post-run-command
        needs: non-existent-command
        if: ${{ always() }}
        run: echo "this thing works!"

      - id: another-post-run-command
        needs: non-existent-command
        if: ${{ always() }}
        run: echo "this thing works again!"
        working-directory: not-required-but-you-can-provide-it

      - id: non-existent-command
        name: 'Running an non-existing command will fail...'
        run: run something that does not exist;

I think your solution is working if you create a plain simple github action workflow.
But this action does add the ability to add a post action for a custom github composer action.
Normally you would have to create a github javascript action to achieve this.

Check out my repo where I successfully use this action: https://github.com/swissbuechi/action-openvpn-client