-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
[cli] Add vercel bisect
command
#5778
Conversation
vercel bisect
commandvercel bisect
command
This PR currently has a merge conflict. Please resolve this and then re-add the |
c3ddd8e
to
cd96986
Compare
Codecov Report
@@ Coverage Diff @@
## main #5778 +/- ##
=======================================
Coverage 49.45% 49.45%
=======================================
Files 134 134
Lines 5381 5381
Branches 1350 1350
=======================================
Hits 2661 2661
Misses 2712 2712
Partials 8 8
Continue to review full report at Codecov.
|
if (exitCode === 0) { | ||
color = chalk.green; | ||
action = 'good'; | ||
} else if (exitCode === 125) { |
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.
Do we need to document this exit code?
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.
Yes
Co-authored-by: Steven <steven@ceriously.com>
@@ -133,6 +133,13 @@ export type Deployment = { | |||
created: number; | |||
createdAt: number; | |||
creator: { uid: string; username: string }; | |||
target: string | null; |
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.
target: string | null; | |
target: string | null | undefined; |
This PR adds a new
vercel bisect
command which is inspired bygit bisect
. This command takes two deployment URLs as its input (one "bad" deployment that exhibits a bug, and one "good" deployment where the bug does not occur) and steps through the deployments using a binary search. The command is useful for finding a deployment (and commit if the project is connected to a Git repo) where a bug has been introduced.