GitLab API

GitlabTool
Join our community

Actions1000

Overview

This node operation retrieves the signature information of a specific commit in a GitLab project repository. It is useful for verifying the authenticity and integrity of commits by checking their cryptographic signatures. Common scenarios include auditing commit signatures for security compliance or validating signed commits in a CI/CD pipeline.

Use Case Examples

  1. Fetch the signature of a commit identified by its SHA in a GitLab project to verify its authenticity.
  2. Use in automated workflows to ensure commits are signed before deployment.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request, useful for public repositories or testing.
Authentication Type of authentication used, defaulting to GitLab API key authentication.
baseUrl Base URL of the GitLab instance, defaulting to https://gitlab.com.
Method HTTP method to use for the request, default is GET.
Path Parameters Parameters to specify the project ID or URL-encoded path and the commit SHA or branch/tag name to identify the commit.

Output

JSON

  • signature - The cryptographic signature details of the specified commit
  • commit
    • id - The commit SHA identifier
    • message - The commit message
    • author_name - Name of the commit author
    • author_email - Email of the commit author
    • created_at - Timestamp when the commit was created

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure the project ID and commit SHA are correctly specified and URL-encoded if necessary.
  • Verify that the GitLab API key credential has sufficient permissions to access the repository and commit data.
  • If skipping authentication, confirm the repository is public and accessible without credentials.
  • Common error messages include 404 Not Found if the project or commit does not exist, and 401 Unauthorized if authentication fails.

Links

Discussion