Is your feature request related to a problem? Please describe.
Sometimes, multi-commit PRs require a summary PR description that does not match the first commit's message. This requires manual modification of the PR description, which would get overwritten on the next revup upload, unless the --no-update-pr-body option is provided.
However, sometimes you do want to update PR bodies for other PRs in your stack. This requires you to manually upload the topics that you don't want to update the body for with the flag set, and then upload the rest of the topics without the flag. And even if you only have 1 PR in your stack, it's easy to forget the flag, causing you to erase your custom description accidentally.
Describe the solution you'd like
Add a commit message flag (similar to Topic, Reviewers, etc.) that prevents the PR body from being updated for the given commits that it's set for. This could be something like UpdateBody: false, which would be true by default.
Describe alternatives you've considered
Manual alternatives described in problem statement, but they are not convenient and easy to forget.
Is your feature request related to a problem? Please describe. Sometimes, multi-commit PRs require a summary PR description that does not match the first commit's message. This requires manual modification of the PR description, which would get overwritten on the next
revup upload, unless the--no-update-pr-bodyoption is provided.However, sometimes you do want to update PR bodies for other PRs in your stack. This requires you to manually upload the topics that you don't want to update the body for with the flag set, and then upload the rest of the topics without the flag. And even if you only have 1 PR in your stack, it's easy to forget the flag, causing you to erase your custom description accidentally.
Describe the solution you'd like Add a commit message flag (similar to
Topic,Reviewers, etc.) that prevents the PR body from being updated for the given commits that it's set for. This could be something likeUpdateBody: false, which would betrueby default.Describe alternatives you've considered Manual alternatives described in problem statement, but they are not convenient and easy to forget.