gitlab_rebase_merge_request
Rebase a GitLab merge request onto the target branch to resolve out-of-date status. Requires fast-forward merge, no conflicts, and developer access. Works with project ID and MR number.
Instructions
Rebase MR onto target branch Returns: Rebase status Use when: MR is behind target branch Fixes: Out-of-date MR status
Requirements:
Fast-forward merge method
No conflicts
Developer access
Related tools:
gitlab_get_merge_request: Check if rebase needed
gitlab_merge_merge_request: Merge after rebase
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mr_iid | Yes | Merge request number (IID - Internal ID) Type: integer Format: Project-specific MR number (without !) Required: Yes Examples: - 456 (for MR !456) - 7890 (for MR !7890) How to find: Look at MR URL or title - URL: https://gitlab.com/group/project/-/merge_requests/456 → use 456 - Title: "Add new feature (!456)" → use 456 Note: This is NOT the global MR ID | |
| project_id | No | Project identifier (auto-detected if not provided) Type: integer OR string Format: numeric ID or 'namespace/project' Optional: Yes - auto-detects from current git repository Examples: - 12345 (numeric ID) - 'gitlab-org/gitlab' (namespace/project path) - 'my-group/my-subgroup/my-project' (nested groups) Note: If in a git repo with GitLab remote, this can be omitted |