I think this is the reason why some CLs have more than one Gerrit
CL.
Given that using the same change to open a fresh new gerrit CL is
rarely needed, I think git-codereview should error out if the user
deletes the Change-Id: line (with git change).
And we can add a -f option to override the error (I'm also fine with
let the user git commit --amend to manually remove the Change-Id.)
Of course, git-codereview probably can't detect the case where
the user has used git commit --amend to remove the Change-Id,
but our contribution guideline uses git change, so the proposed
check should catch most problems.
I think this is the reason why some CLs have more than one Gerrit
CL.
Given that using the same change to open a fresh new gerrit CL is
rarely needed, I think git-codereview should error out if the user
deletes the Change-Id: line (with git change).
And we can add a -f option to override the error (I'm also fine with
let the user
git commit --amendto manually remove the Change-Id.)Of course, git-codereview probably can't detect the case where
the user has used
git commit --amendto remove the Change-Id,but our contribution guideline uses git change, so the proposed
check should catch most problems.