GitLab API

GitlabTool
Join our community

Actions905

Overview

This node operation retrieves the signature of a specific commit in a GitLab project repository using the GitLab API v4. It is useful for verifying the authenticity and integrity of commits by fetching their cryptographic signatures. Common scenarios include automated verification of commit signatures in CI/CD pipelines or auditing commit authenticity in project repositories.

Use Case Examples

  1. Fetch the signature of a commit identified by its SHA in a specific GitLab project to verify its authenticity.
  2. Use in a workflow to automatically check commit signatures before deployment to ensure code integrity.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request, useful for public repositories or unauthenticated access.
Authentication Type of authentication used, here it is GitLab API authentication, hidden if Skip Authentication is true.
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 required in the request path to identify the project and commit.

Output

JSON

  • signature - The cryptographic signature of the specified commit.
  • commitId - The SHA identifier of the commit for which the signature was retrieved.
  • verificationStatus - Status indicating whether the commit signature is valid, invalid, or unverified.

Dependencies

  • GitLab API authentication token or credentials

Troubleshooting

  • Ensure the project ID and commit SHA are correctly specified and URL-encoded if necessary.
  • Authentication errors may occur if the GitLab API token is missing, expired, or lacks sufficient permissions.
  • If the commit does not have a signature, the response may be empty or indicate no signature found.

Links

Discussion