a68769eb4f
Commits can be rejected due to the following issues in the commit message: - Change-Id tag is missing or incorrectly formatted - Multiple Change-Id tags are present - Signed-off-by tag is missing or does not specify the correct user However the error messages raised in these cases do not make it clear that the required tags are expected to be found in the footer (last paragraph) of the commit message. Update the error messages and related documentation to explicitly mention that the tags should be in the commit message footer. Change-Id: I7d2d2dfb66bed3697745733c4fe19c177e9bc56b
32 lines
1.2 KiB
Plaintext
32 lines
1.2 KiB
Plaintext
invalid Change-Id line format in commit message footer
|
|
======================================================
|
|
|
|
With this error message Gerrit rejects to push a commit if its commit
|
|
message footer contains an invalid Change-Id line.
|
|
|
|
You can see the commit messages for existing commits in the history
|
|
by doing a link:http://www.kernel.org/pub/software/scm/git/docs/git-log.html[git log].
|
|
|
|
If it was the intention to rework a change and to push a new patch
|
|
set, find the change in the Gerrit WebUI, copy its Change-Id line and
|
|
use it to correct the invalid Change-Id line in the commit message of
|
|
the commit for which the push is failing. How to do this is explained
|
|
link:error-push-fails-due-to-commit-message.html#commit_hook[here].
|
|
|
|
If it was the intention to create a new change in Gerrit simply
|
|
remove the invalid Change-Id line from the commit message of the
|
|
commit for which the push is failing. How to do this is explained
|
|
link:error-push-fails-due-to-commit-message.html#commit_hook[here]. In case you have configured the link:cmd-hook-commit-msg.html[commit hook] a new valid
|
|
Change-Id will be automatically generated and inserted.
|
|
|
|
|
|
SEE ALSO
|
|
--------
|
|
|
|
* link:user-changeid.html[Change-Id Lines]
|
|
|
|
|
|
GERRIT
|
|
------
|
|
Part of link:error-messages.html[Gerrit Error Messages]
|