Class RebaseInput
java.lang.Object
com.google.gerrit.extensions.api.changes.RebaseInput
-
Field Summary
FieldsModifier and TypeFieldDescriptionboolean
Whether the rebase should succeed if there are conflicts.Rebase will be committed using this email address.boolean
Whether the rebase should be done on behalf of the uploader.strategy
name of the merge strategy. -
Constructor Summary
Constructors -
Method Summary
-
Field Details
-
base
-
strategy
strategy
name of the merge strategy.- See Also:
-
MergeStrategy
-
allowConflicts
public boolean allowConflictsWhether the rebase should succeed if there are conflicts.If there are conflicts the file contents of the rebased change contain git conflict markers to indicate the conflicts.
-
onBehalfOfUploader
public boolean onBehalfOfUploaderWhether the rebase should be done on behalf of the uploader.This means the uploader of the current patch set will also be the uploader of the rebased patch set. The calling user will be recorded as the real user.
Rebasing on behalf of the uploader is only supported for trivial rebases. This means this option cannot be combined with the
allowConflicts
option.In addition, rebasing on behalf of the uploader is only supported for the current patch set of a change and not when rebasing a chain.
Using this option is not supported when rebasing a chain via the Rebase Chain REST endpoint.
-
validationOptions
-
committerEmail
Rebase will be committed using this email address. Only the registered emails of the calling user or uploader (when onBehalfOfUploader is true) are considered valid.This option is not supported when rebasing a chain.
-
-
Constructor Details
-
RebaseInput
public RebaseInput()
-