Skip to content
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

x/review/git-codereview: support WIP mode #20991

Closed
andybons opened this issue Jul 12, 2017 · 6 comments
Closed

x/review/git-codereview: support WIP mode #20991

andybons opened this issue Jul 12, 2017 · 6 comments
Labels
FrozenDueToAge help wanted NeedsFix The path to resolution is known, but the work has not been done.
Milestone

Comments

@andybons
Copy link
Member

Work-in-progress mode is nice for when you want to upload a change but make it clear that it’s not ready for review.

https://gerrit-review.googlesource.com/Documentation/user-upload.html#wip

@andybons andybons self-assigned this Jul 12, 2017
@gopherbot gopherbot added this to the Unreleased milestone Jul 12, 2017
@josharian
Copy link
Contributor

Nice. How does this show up in the gerrit UI? Does it make the CL invisible to others, or just mark it somehow? Note that this is approximated today by putting the words "DO NOT REVIEW" in the commit message.

@andybons
Copy link
Member Author

Looks like this:
screen shot 2017-07-12 at 3 40 03 pm

@rsc
Copy link
Contributor

rsc commented Sep 22, 2017

If this is meant to be approximately the same as 'DO NOT REVIEW', then let's make git-codereview automatically set the WIP bit for 'DO NOT REVIEW' CLs, or maybe we can even write some logic in the Gerrit config to do that. People already understand 'DO NOT REVIEW' and 'DO NOT SUBMIT'. I'd like to be able to keep using them, and in particular I'd like to be able to keep storing the setting in the CL description itself - in contrast to a git mail command-line flag like we have for --trybot - because I can write that down during commit time, working offline, instead of having to remember to do it later when I eventually git mail. (It would be especially bad if I had to remember every time I run git mail.)

Note also that you can have a CL stack where only some of the CLs are 'DO NOT REVIEW'. The implementation in git-codereview will have to be careful to get the bits right on the individual CLs in the stack. This another reason to keep the bits in the CL descriptions and not be a different mail mode. (It's unclear to me that push %wip handles this at all, but for a multiple-CL push, maybe git-codereview can go back after the push and set the WIP bits individually through the REST API.)

@andybons
Copy link
Member Author

Until https://bugs.chromium.org/p/chromium/issues/detail?id=750933 gets fixed I’d like to hold off on this.

@andybons andybons added help wanted NeedsFix The path to resolution is known, but the work has not been done. labels Feb 16, 2018
@andybons andybons removed their assignment Feb 16, 2018
@kardianos
Copy link
Contributor

@gopherbot
Copy link

Change https://golang.org/cl/233237 mentions this issue: git-codereview: add -wip flag to mail command

@golang golang locked and limited conversation to collaborators May 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
FrozenDueToAge help wanted NeedsFix The path to resolution is known, but the work has not been done.
Projects
None yet
Development

No branches or pull requests

5 participants