| Issue 453: | Detect and warn when submitting a change that doesn't affect any files. | |
| 3 people starred this issue and may be notified of changes. | Back to list |
Imagine this scenario: 1. Configure repository for cherry-pick mode 2. Submit a new change A 3. Submit the same commit as another new change B (accidentally... this happens quite often for people not using the commit hook to add Change-Id) 4. Submit both changes A and B (again, presumably accidentally) Both changes will appear in the repo, but the one submitted second will actually be an empty commit with just a commit message and no diff. It would be nice if Gerrit could determine that a change being submitted didn't actually change any files, and offer a warning to the user. I can imagine a scenarios where just having a commit in the history with no file changes is meaningful so I don't think we'd want to reject it outright, but it seems like most of the time when this happens it's because of user error.
Feb 18, 2010
#1
sop@google.com
Status:
Accepted
|
|
| ► Sign in to add a comment |