-
Notifications
You must be signed in to change notification settings - Fork 405
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
ci: fix frontend deploy workflow #4977
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 3 Skipped Deployments
|
Docker builds report
|
Uffizzi Preview |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4977 +/- ##
=======================================
Coverage 97.39% 97.39%
=======================================
Files 1191 1191
Lines 41630 41630
=======================================
Hits 40546 40546
Misses 1084 1084 ☔ View full report in Codecov by Sentry. |
env: | ||
VERCEL_PROJECT_ID: ${{ secrets.VERCEL_PROJECT_ID }} | ||
VERCEL_ORG_ID: ${{ secrets.VERCEL_ORG_ID }} | ||
ENV: prod |
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.
I think it might be worth mentioning this is a production workflow in the filename if this isn't an input
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.
Yeah, fair point. I've added an input for this as I hope that we can use this for staging in the future rather than having different workflows for staging / production and demo.
Changes
Fixes frontend deployment workflow, and refactors for code reuse.
How did you test this code?
Triggered the workflow (without actually deploying) for the new branch (see here)