Fix problems with `rbt status-update set` and documentation.
Review Request #14056 — Created July 26, 2024 and submitted
The documentation for creating reviews with
rbt status-update set
indicated that body_top and body_bottom content should be set inside of
areview
key in the JSON file, but the actual implementation was using
reviews
.review
is much more appropriate, so I've changed the
implementation to match the documentation.This also adds
issue_opened
as a field for general comments in the
documentation. Because of how we create comments, any field that's valid
for the comment resource will work, but it was confusing to list
issue_opened
under diff comments but not general comments.
Posted a review using
rbt status-update set
that included body top and
body bottom content, and saw that that content was properly reflected in
the rendered status update.
Summary | ID |
---|---|
e89dcd9328db1f38c453b403b1ba30723bb220cb |
Description | From | Last Updated |
---|---|---|
Given the change, do we want to look for both keys, maybe deprecate the old? |
|