3fc69ca36a
Users can still upload a new patch set by explicitly pushing a commit to a change by specifying it as target ref. E.g.: git push origin HEAD:refs/changes/711 If the specified change belongs to another project, Gerrit rejects the push with the error message "change ... not found". This error message is incorrect since the change actually exists in Gerrit. This change now provides a better error message for this case: "change ... does not belong to project ...". In addition it adds a documentation page that explains this error. Change-Id: I806acba774f8a1c6c0a6439e92314993f0ab4289 Signed-off-by: Edwin Kempin <edwin.kempin@sap.com>
17 lines
636 B
Plaintext
17 lines
636 B
Plaintext
change ... does not belong to project ...
|
|
=========================================
|
|
|
|
With this error message Gerrit rejects to push a commit to a change
|
|
that belongs to another project.
|
|
|
|
This error message means that the user explicitly pushed a commit to
|
|
a change that belongs to another project by specifying it as target
|
|
ref. This way of adding a new patch set to a change is deprecated as
|
|
explained link:user-upload.html#manual_replacement_mapping[here]. It is recommended to only rely on Change-ID's for
|
|
link:user-upload.html#push_replace[replacing changes].
|
|
|
|
|
|
GERRIT
|
|
------
|
|
Part of link:error-messages.html[Gerrit Error Messages]
|