-
Notifications
You must be signed in to change notification settings - Fork 370
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
Fix vercel redeploy #4119
Fix vercel redeploy #4119
Conversation
Now it's clear what the problem was: https://github.com/rerun-io/rerun/actions/runs/6721155529/job/18266251435#step:3:13 |
Seems to work after giving it a fresh token |
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.
Thanks for improving the error reporting around this!
|
||
console.log(`Triggering redeploy`); | ||
await client.redeploy(team.id, deployment.uid, "landing"); | ||
info`Fetching team "${teamName}"`; |
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.
What magic syntax is this O.o
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.
One last thing: Added the ability to run the deployment manually given all the same inputs as the CI, via |
What
Checklist