-
Notifications
You must be signed in to change notification settings - Fork 42
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
Populate and enforce last_status_number column of backend #758
Populate and enforce last_status_number column of backend #758
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
Code looks good - sorry for the nits, but it looks like the terms last_status
, current_status
, and new_status
are being used in slightly confusing ways. Mind if we stick to the two terms last_status
and new_status
(or next_status
) while in that function?
This bails from updating the backend status if the existing status is greater or equal to the new status.
If the existing
last_status_number
isNULL
, this will always succeed.