![]() ![]() So I needed to give the GitHub repository that is running this actions access to the environment variable by going to its settings page. ![]() In particular the GitHub Action workflow did not have access to the FONTAWESOME_NPM_AUTH_TOKEN which I have set in my local bash profile and passed into the. ![]() However, I merged the pull request with my changes and saw on the Pull Request that the step of the GitHub Action workflow that installed dependencies failed with the following error:ΔΆ ///:_authToken=$ In order to setup my GitHub Action, I modeled my new GitHub Action workflow after similar functional workflows and expected everything to run smoothly. Hopefully this article saves you some time and build minutes the next time you set up environment variables for GitHub Actions. I went through a few of my GitHub Actions build minutes while testing how to properly pass environment variables to my. I ran into some hiccups when setting it up so that the workflow could install the Font Awesome dependency which requires an NPM token. I recently set up GitHub actions on this site to automatically run unit tests whenever I open a new Pull Request to ensure that changes to the site were not introduction breaking changes to unit tests under the radar. This article walks through how to pass environment variables to GitHub Action Workflows.
0 Comments
Leave a Reply. |