GitLab API

GitlabTool

Actions905

Overview

This node operation retrieves the list of commits associated with a specific merge request in a GitLab project. It is useful for developers and DevOps teams who want to track changes, review commit history, or automate workflows based on merge request commits. For example, it can be used to fetch commits for code review automation or to trigger CI/CD pipelines based on commit data.

Use Case Examples

  1. Fetch commits of a merge request to display in a dashboard.
  2. Automate code quality checks on commits of a merge request.
  3. Generate reports on merge request activity by analyzing commit history.

Properties

Name Meaning
Skip Authentication Whether to skip authentication for the request.
Authentication The authentication method used for the request, typically an API key credential.
baseUrl The base URL of the GitLab instance to which the request is sent.
Method The HTTP method used for the request.
Path Parameters Parameters used in the request path to specify the project and merge request.

Output

JSON

  • commit_id - The unique identifier of the commit.
  • author_name - The name of the commit author.
  • author_email - The email of the commit author.
  • message - The commit message.
  • created_at - The timestamp when the commit was created.

Dependencies

  • GitLab API authentication token

Troubleshooting

  • Ensure the project ID and merge request IID are correctly specified; incorrect values will result in errors or empty responses.
  • Authentication errors may occur if the API token is missing or invalid; verify credentials are correctly configured.
  • Network or base URL misconfiguration can cause request failures; confirm the baseUrl is correct for your GitLab instance.

Links

Discussion