GitLabMergeOptions
Current GitLab project policy, readiness, defaults and linked follow-ups.
GitLabMergeOptionsFields
Numeric GitLab target project identifier.
Project-scoped merge-request number.
Merge-request title.
Current merge-request state or durable merge-operation lifecycle state.
Source commit reviewed in the sheet; submission rejects a changed commit.
Source branch of the merge request.
Target branch of the merge request.
Read-only project merge method: merge, rebase_merge or ff.
Project squash policy: always, never, default_on or default_off.
Whether to squash source commits when merging.
Whether GitLab should remove the remote source branch after merge.
Whether the source-branch removal choice is editable.
Whether current provider requirements permit an immediate merge.
Whether native auto-merge can be enabled for the current request.
Whether the current user may cancel enabled auto-merge.
Whether GitLab currently reports native auto-merge enabled.
Reason an immediate merge is unavailable, when known.
Reason enabling auto-merge is unavailable, when known.
Optional merge-commit message override; null preserves GitLab defaults.
Optional squash-commit message override; null preserves GitLab defaults.
Linked source checkout, when one exists.
Display path of the linked checkout.
Whether a matching non-primary checkout can be selected for safe cleanup.
Linked Jira issue key.
Whether the linked Jira project has a configured done status.
Previously selected Jira follow-up, false for new merge operations.
Previously selected worktree cleanup, false for new merge operations.
Persisted merge intent and follow-up outcome, when available.