"Specifies a named branch or tag reference with its expected HEAD \'hash\' value.\n\nFor example:\n- name@hash - Identifies the \'hash\' commit on a branch or tag.\n\nThe specified \'hash\' must be the value of the current HEAD of the branch or tag known by the client. It will be used to validate that at execution time the reference points to the same hash that the caller expected when the operation arguments were constructed.\n"
"The \'ref\' parameter may contain a hash qualifier. That hash as well as the optional \'type\' parameter may be used to ensure the operation is performed on the same object that the user expects.\n"
"A reference to a particular version of the contents tree (a point in history) on a branch.\nThis reference is specified in this form:\n- name@hash - Identifies the \'hash\' commit on the named branch.\n\nThe \'hash\' commit must be reachable from the current HEAD of the branch.\nIn this case \'hash\' indicates the state of contents that should be used for validating incoming changes.\n"
"The default merge mode. If not set, `NORMAL` is assumed.\n\nThis settings applies to key thaWhen set to \'true\' instructs the server to validate the request\n but to avoid committing any changes.t are not explicitly mentioned in the `keyMergeModes` property.\n"
"When set to \'true\' instructs the server to validate the request but to avoid committing any changes.\n"
"Whether to provide optional response data.\n"
"The name of the reference that contains the \'source\' commits for the requested merge or transplant operation.\n"
"The \'name@hash\' form always refers to the exact commit on a specific named reference. This is the most complete form of a reference. Other forms omit some of the details and require those gaps to be filled by the server at runtime. Although these forms may be convenient to a human-being, they may resolve differently at different times depending on the state of the system. Using the full \'name@hash\' form is recommended to avoid ambiguity.\n"
"Key components (namespaces) are separated by the dot (\'.\') character. Dot (\'.\') characters that are not Nessie namespace separators must be encoded as the \'group separator\' ASCII character (0x1D).\n"
"The upper bound of the content key range to retrieve (inclusive). The content keys of all returned entries will be less than or equal to the max-value. Content-keys are compared as a \'whole\', unlike prefix-keys.\n\nKey components (namespaces) are separated by the dot (\'.\') character. Dot (\'.\') characters that are not Nessie namespace separators must be encoded as the \'group separator\' ASCII character (0x1D).\n"
"Specific merge behaviour requests by content key.\n\nThe default is set by the `defaultKeyMergeMode` parameter.\n"
"The lower bound of the content key range to retrieve (inclusive). The content keys of all returned entries will be greater than or equal to the min-value. Content-keys are compared as a \'whole\', unlike prefix-keys.\n\nKey components (namespaces) are separated by the dot (\'.\') character. Dot (\'.\') characters that are not Nessie namespace separators must be encoded as the \'group separator\' ASCII character (0x1D).\n"
"The key to a content object.\n\nKey components (namespaces) are separated by the dot (\'.\') character. Dot (\'.\') characters that are not Nessie namespace separators must be encoded as the \'group separator\' ASCII character (0x1D).\n"
"The content key prefix to retrieve (inclusive). A content key matches a given prefix, a content key\'s elements starts with all elements of the prefix-key. Key prefixes exactly match key-element boundaries.\n\nMust not be combined with min/max-key parameters.\n\nKey components (namespaces) are separated by the dot (\'.\') character. Dot (\'.\') characters that are not Nessie namespace separators must be encoded as the \'group separator\' ASCII character (0x1D).\n"
"A reference to a specific version of the contents tree (a point in history) on a branch.\nThis reference is specified in this form:\n- name@hash - Identifies the \'hash\' commit on the named branch.\n\nThe \'hash\' commit must be reachable from the current HEAD of the branch.\nIn this case \'hash\' indicates the state of contents known to the client and serves to ensure that the operation is performed on the contents that the client expects.\nThis hash can point to a commit in the middle of the change history, but it should be as recent as possible.\n"
"To implement paging, check \'hasMore\' in the response and, if \'true\', pass the value returned as \'token\' in the next invocation as the \'pageToken\' parameter.\n\nThe content and meaning of the returned \'token\' is \"private\" to the implementation,treat is as an opaque value.\n\nIt is wrong to assume that invoking this method with a very high \'maxRecords\' value will return all available data in one page.\n\nDifferent pages may have different numbers of log records in them even if they come from another call to this method with the same parameters. Also, pages are not guaranteed to be filled to contain exactly \'maxRecords\' even if the total amount of available data allows that. Pages may contain more of less entries at server\'s discretion.\n"
"Specifies a reference to a particular commit history branch or tag.\n\nThis reference can be specification in these forms:\n- \\- (literal minus character) - identifies the default branch.\n- name - Identifies the named branch or tag.\n"
"A reference name.\n\nReference name must start with a letter, followed by letters, digits, one of the ./_- characters, not end with a slash or dot, not contain \'..\'\n"
"A reference to a particular version of the contents tree (a point in history).\n\nReference representations consist of:\n- The reference name. \'-\' means the default branch name.\n- A commit hash prefixed with \'@\'.\n- A relative commit specification. \'~N\' means the N-th predecessor commit, \'*T\' means the commit for which the timestamp T (milliseconds since epoch or ISO-8601 instant) is valid, \'^N\' means the N-th parentin a commit (N=2 is the merge parent).\n\nIf neither the reference name or the default branch name placeholder \'-\' is specified, the reference type \'DETACHED\' will be assumed.\nIf no commit hash is specified, the HEAD of the specified named reference will be used.\nAn empty reference parameter is not valid.\n\nThis reference can be specified in these forms:\n- \\- (literal minus character) - identifies the HEAD of the default branch.\n- name - Identifies the HEAD commit of a branch or tag.\n- name@hash - Identifies the \'hash\' commit on a branch or tag.\n- @hash - Identifies the \'hash\' commit in an unspecified branch or tag.\n- -~3 - The 3rd predecessor commit from the HEAD of the default branch.\n- name~3 - The 3rd predecessor commit from the HEAD of a branch or tag.\n- @hash~3 - The 3rd predecessor commit of the \'hash\' commit.\n- name@hash^2 - The merge parent of the \'hash\' commit of a branch or tag.\n- @hash^2 - The merge parent of the \'hash\' commit.\n- -*2021-04-07T14:42:25.534748Z - The predecessor commit closest to the HEAD of the default branch for the given ISO-8601 timestamp.\n- name*2021-04-07T14:42:25.534748Z - The predecessor commit closest to the HEAD of a branch or tag valid for the given ISO-8601 timestamp.\n- name*1685185847230 - The predecessor commit closest to the HEAD of a branch or tag valid for the given timestamp in milliseconds since epoch.\n\nIf both \'name\' and \'hash\' are given, \'hash\' must be reachable from the current HEAD of the branch or tag. If \'name\' is omitted, the reference will be of type \'DETACHED\' (referencing a specific commit hash without claiming its reachability from any live HEAD). Using references of the last form may have authorization implications when compared to an equivalent reference of the former forms.\n\nAn empty reference parameter is invalid.\n\nThe \'name@hash\' form always refers to the exact commit on a specific named reference. This is the most complete form of a reference. Other forms omit some of the details and require those gaps to be filled by the server at runtime. Although these forms may be convenient to a human-being, they may resolve differently at different times depending on the state of the system. Using the full \'name@hash\' form is recommended to avoid ambiguity.\n"
"Restrict the result to one or more keys.\n\nCan be combined with min/max-key and prefix-key parameters, however both predicates must match. This means that keys specified via this parameter that do not match a given min/max-key or prefix-key will not be returned.\n\nKey components (namespaces) are separated by the dot (\'.\') character. Dot (\'.\') characters that are not Nessie namespace separators must be encoded as the \'group separator\' ASCII character (0x1D).\n"
"When set to \'true\' instructs the server to produce normal (non-error) responses in case a conflict is detected and report conflict details in the response payload."
"Whether to return the documentation, if it exists. Default is to not return the documentation."