| Issue 361: | comment on the commit message | |
| 15 people starred this issue and may be notified of changes. | Back to list |
Today it's very easy and functional to be navigate and provide feedback to a code review in any order. You can review any files you wish, comment on any lines you wish, review your comments, and revise your comments, in any order, and even in multiple sessions. But none of this is true for the "master" comment. You get a single shot to edit the master comment, when you are ready to submit. Often times the master comment is the most important one, because it's where you'd like to discuss global issues about the change. It's also sometimes the *first* place you might want to make comments, if you have comments about the changelist description. My feature request is to make the "master" comment editable and revisable at any time during the review process. I have been using "line 1 of the first file" as a hack workaround for this. Yecch.
Aug 19, 2010
Fixed by I11004eddfa7ab10e6491eedcf437771bf1e5af64
Status:
Fixed
Labels: FixedIn-2.1.5
Mar 27, 2012
(No comment was entered for this change.)
Status:
Released
May 17, 2012
This seems to have been regressed sometime between 2.1.7.2 and 2.3. I don't see anyway to comment on commit messages any long, as the commit message shows up in the diff viewer as "No Differences".
Jun 13, 2012
Probably this was fixed by [1]. This fix was cherry-picked for the upcoming 2.4.1 release. [1] https://gerrit-review.googlesource.com/35650 |
|
| ► Sign in to add a comment |
Status: Accepted