gitlab_get_user_merge_commits

Track merge commits performed by a specific user in GitLab to monitor merge activity, analyze workflows, and ensure quality assurance. Filter by user, project, branch, or timeframe for targeted insights.

Instructions

List merge commits where a specific user performed the merge.

Shows commits where the user merged branches (not necessarily the code author). Use this tool to see what merges a user has performed, useful for release management.

Examples:

Release management: get_user_merge_commits(user_id=123)
Merge activity tracking
Integration oversight

For all commits authored by user, use 'gitlab_get_user_commits' instead.

Find all commits that originated from merge requests created by the specified user, tracking their integrated contributions.

Returns merge-related commits with:

Commit details: SHA, message, merge info
MR context: original MR, review process
Integration info: target branch, merge strategy
Quality metrics: review feedback, CI results
Timeline: development to integration time

Use cases:

Track integrated contributions
Measure code review effectiveness
Analyze development workflows
Quality assurance reporting

Parameters:

user_id: Numeric user ID
username: Username string (use either user_id or username)
project_id: Optional project scope filter
target_branch: Filter by target branch (e.g., main)
since: MRs merged after date (YYYY-MM-DD)
until: MRs merged before date (YYYY-MM-DD)
include_review_metrics: Include review statistics
per_page: Results per page (default: 20)
page: Page number (default: 1)

Example: Get merged contributions to main branch

{
  "username": "johndoe",
  "target_branch": "main", 
  "since": "2024-01-01",
  "include_review_metrics": true
}

Input Schema

Name	Required	Description
`page`	No	Page number for pagination Type: integer Range: ≥1 Default: 1 Example: 3 (to get the third page of results) Note: Use with per_page to navigate large result sets
`per_page`	No	Number of results per page Type: integer Range: 1-100 Default: 20 Example: 50 (for faster browsing) Tip: Use smaller values (10-20) for detailed operations, larger (50-100) for listing
`project_id`	No	Optional project scope filter
`since`	No	Commits after date (YYYY-MM-DD)
`until`	No	Commits before date (YYYY-MM-DD)
`username`	Yes	Username string

Input Schema (JSON Schema)

{
  "properties": {
    "page": {
      "default": 1,
      "description": "Page number for pagination\nType: integer\nRange: ≥1\nDefault: 1\nExample: 3 (to get the third page of results)\nNote: Use with per_page to navigate large result sets",
      "minimum": 1,
      "type": "integer"
    },
    "per_page": {
      "default": 50,
      "description": "Number of results per page\nType: integer\nRange: 1-100\nDefault: 20\nExample: 50 (for faster browsing)\nTip: Use smaller values (10-20) for detailed operations, larger (50-100) for listing",
      "maximum": 100,
      "minimum": 1,
      "type": "integer"
    },
    "project_id": {
      "description": "Optional project scope filter",
      "type": "string"
    },
    "since": {
      "description": "Commits after date (YYYY-MM-DD)",
      "type": "string"
    },
    "until": {
      "description": "Commits before date (YYYY-MM-DD)",
      "type": "string"
    },
    "username": {
      "description": "Username string",
      "type": "string"
    }
  },
  "required": [
    "username"
  ],
  "type": "object"
}

MCP GitLab Server