Skip to content

Conversation

@trotterdylan
Copy link
Contributor

The command operates as follows:

  • Fetch the review associated with the current commit
  • Traverse up the stack by fetching that review's latest revision's parent
  • Traverse each of these reviews in reverse order and do:
    • syncReviewWithParent to update the review
    • If an update happened, fetch the updated remote branch
  • Update the current HEAD branch to point to the top of the stack.

Basically it works its way up the stack, updating each review upon the last.
In the event that a parent review was merged, rebased, etc. then the child
review will be rebased accordingly. At the end of this process, the whole
stack of reviews will be up to date on plz.review, and the origin branches in
the local repo will be up to date with GitHub.

What this command does not do is incorporate any local changes. I have some
ideas but it's still a little fuzzy how best to handle it in an intuitive way.

plz-review-url: https://plz.review/review/4914

@plz-review
Copy link

plz-review bot commented Mar 28, 2022

Plz review!

@trotterdylan trotterdylan requested a review from lyndonoc March 28, 2022 12:37
@trotterdylan trotterdylan force-pushed the plz.review/review/4913 branch from f5e4143 to 287473c Compare March 28, 2022 19:03
@trotterdylan trotterdylan force-pushed the plz.review/review/4914 branch from 751f5cb to b8a8502 Compare March 28, 2022 19:03
@plz-review plz-review bot force-pushed the plz.review/review/4913 branch from 287473c to 4dfb5e2 Compare March 28, 2022 19:03
Base automatically changed from plz.review/review/4913 to main March 28, 2022 19:09
The command operates as follows:

* Fetch the review associated with the current commit
* Traverse up the stack by fetching that review's latest revision's parent
* Traverse each of these reviews in reverse order and do:
  - syncReviewWithParent to update the review
  - If an update happened, fetch the updated remote branch
* Update the current HEAD branch to point to the top of the stack.

Basically it works its way up the stack, updating each review upon the last.
In the event that a parent review was merged, rebased, etc. then the child
review will be rebased accordingly.  At the end of this process, the whole
stack of reviews will be up to date on plz.review, and the origin branches in
the local repo will be up to date with GitHub.

What this command does *not* do is incorporate any local changes. I have some
ideas but it's still a little fuzzy how best to handle it in an intuitive way.

plz-review-url: https://plz.review/review/4914
@plz-review plz-review bot force-pushed the plz.review/review/4914 branch from b8a8502 to 6a2ca4a Compare March 28, 2022 19:09
Copy link
Contributor

@lyndonoc lyndonoc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@trotterdylan trotterdylan merged commit 85935ed into main Mar 28, 2022
@trotterdylan trotterdylan deleted the plz.review/review/4914 branch March 28, 2022 19:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants