Thanks a lot, this worked without problems!

I saw this page before but somehow thought that it only applied to the Node.js toolkit.

The cited documentation suggests the modification is seen by all subsequent steps in the job.  So it would seem at odds with your assertion that each step is its own process.

I’ve not been able to get ::add-path::/path/to/dir to augment PATH, either within the step or within the job.  Would appreciate sample yaml that augments the PATH variable, as the documentation offers none.

Ultimately had to monkey at the typescript level https://github.com/dickmao/setup-paths to change PATH.

Hi, Is there any documentation about this windows add-path style? From the offical docs, I couldn’t find it.

@d4nte wrote:

It seems like the correct way on Windows is (contrary to the doc):

• name: Add strawperryperl to the PATH to override the existing Perl installation so we can compile OpenSSL locally
  run: echo “##[add-path]C:\strawberry\c\bin;C:\strawberry\perl\site\bin;C:\strawberry\perl\bin”
  if: matrix.os == ‘windows’

Hi, Is there any documentation about this windows add-path style? From the offical docs, I couldn’t find it.

> Each step is run its own process space so environment changes do not automatically propgate.  If you want to update the path you can use the add-path command as documented https://help.github.com/en/articles/development-tools-for-github-actions#add-a-system-path-add-path.  

Your link as countless others out there for the GitHub actions documentation are all dead.

A little bit of googling and here it is: https://help.github.com/en/actions/reference/workflow-commands-for-github-actions#adding-a-system-path

Works, at least at the moment of writing this.