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
gerrit, x/review/git-codereview: give may-forge-author permission to approvers #55841
Comments
I would love to be able to rebase CLs. In particular, when an older CL was reviewed and ready, but I want to re-test it on master before landing it. |
It turns out that our
It seems to me that there's no reason not to grant That still leaves |
I've granted |
In an effort to remove unused permissions, I cleared out @FiloSottile, you were the only active non-Googler in the group as far as I could tell from a quick glance. Would you like me to add you back? |
I do use |
Added. |
The Gerrit team has launched support for trivial rebases without special permissions; you can see an example of @dmitshur using it at https://go-review.git.corp.google.com/c/build/+/477775/6#message-6beb8aa86e9796a603ef6de08318fa52b3ca80ac. I believe that takes care of enough of the use cases for |
Currently, on Gerrit, the "Rebase" and "cherry-pick" buttons on the Gerrit UI require may-forge-author permission, if you're not the author of the original CL. This sometimes causes inconvenience. We are considering giving all Gerrit approvers (who can +2 CLs) may-forge-author permission.
A concern is that one might accidentally mail a CL that overwrites someone else's pending CL. To prevent that we're considering making the
git-codereview
tool check the author before mailing the CL, and adding a flag so if one actually needs to upload a forged CL one can usegit mail -forge
.cc @golang/release @rsc
The text was updated successfully, but these errors were encountered: