New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adopt package-lock.json #40146
Adopt package-lock.json #40146
Conversation
I believe the AzDO pipelines already respect this since they share a task group with the release branches. |
@@ -0,0 +1,27 @@ | |||
name: Update package-lock.json |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@weswigham @andrewbranch Is there a better way to test this than confirming it ran the night after this PR merged?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably, but I don’t think any of them are as good as the way you mentioned. You can add a workflow_dispatch
trigger in addition to the schedule
trigger to be able to run it manually.
Add a workflow to update it daily overnight.