You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've determined that for repos using yarn workspace or repos needing private NPM auth credentials that running the @actions/checkout step will override any prior setup. We added a parameter to the create-update-axe-core-pull-request action to conditionally run the checkout step to handle this. However this solution isn't ideal and we should instead just not check out at all in the public actions. Instead the calling code of the public action should be responsible for checking out the repo and doing setup before calling the action.
In order to do this in piecemeal (so we don't break all the actions) we should:
Add the conditional parameter to every public action that uses the @actions/checkout step
After that, each repo that uses the public action should update their actions to do the checkout / setup step and use the conditional parameter to disable the step in the public action
Once all repos have been converted to this new style we can delete the conditional parameter from the public actions
Lastly we can remove the usage of the conditional parameter in all our other repos
The text was updated successfully, but these errors were encountered:
We've determined that for repos using yarn workspace or repos needing private NPM auth credentials that running the
@actions/checkout
step will override any prior setup. We added a parameter to the create-update-axe-core-pull-request action to conditionally run the checkout step to handle this. However this solution isn't ideal and we should instead just not check out at all in the public actions. Instead the calling code of the public action should be responsible for checking out the repo and doing setup before calling the action.In order to do this in piecemeal (so we don't break all the actions) we should:
@actions/checkout
stepThe text was updated successfully, but these errors were encountered: