[CI] Redundant `npm install` step in release workflow?
Opened this issue · 2 comments
leecalcote commented
Current Behavior
The current release workflow has two steps performing npm install. Is this necessary or is it a redundant step that might be eliminated?
sistent/.github/workflows/release.yml
Line 22 in f0b95c4
Contributor Guides and Resources
- 🛠 Meshery Build & Release Strategy
- 🎨 Wireframes and designs for Layer5 site in Figma (open invite)
- 🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack
nebula-aac commented
It was necessary when I had the error with husky, but not sure now after changing it. I'll review again if this steps is still needed or not.
leecalcote commented
Ok, gotcha.
…On Tue, Feb 13, 2024 at 7:23 AM Antonette Caldwell ***@***.***> wrote:
It was necessary when I had the error with husky, but not sure now after
changing it. I'll review again if this steps is still needed or not.
—
Reply to this email directly, view it on GitHub
<#505 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABZYKEHV7IJGGA65D4DQD2DYTNSLNAVCNFSM6AAAAABDGN62ZWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBRGUYDMNRVHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>