-
Notifications
You must be signed in to change notification settings - Fork 258
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
feat: add new deployment metadata to table #987
feat: add new deployment metadata to table #987
Conversation
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 @Fuzzicles ! Just a small comment.
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.
Sorry for the late review @Fuzzicles ! We're a bit low on review resources because we have some competing priorities coming from a bigger release and an upcoming offsite.
Other than this, the PR is very close.
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.
Just have to test it, looks good to me!
@Fuzzicles Looking good on my side. There could be cases where user has a very long branch name etc, but overall this is good. The upcoming ULID's will also make this prettier :D (For @iulianbarbu) Here are some views of the table at different terminal widths:
|
* feat: add new deployment metadata to table * refactor: review comment --------- Co-authored-by: Grant Lorello <grant.lorello@msn.com>
Description of change
I added the new
git_*
fields to the table output ofcargo shuttle deployment list
.Closes #981
How has this been tested? (if applicable)
I created a new project via the rocket example and made local changes to check that the
git_dirty
field rendered correctly, and that truncating the commit ID and message worked as intended. I also created some deployments with a version prior to the addition of the new metadata to make sure theOption
values correctly displayedNo Data
in the table.