Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node interacts with a Gitea server via its API, specifically focusing on repository-related operations. For the "Repo Signing Key" operation under the "Repository" resource, it retrieves or manages the signing key associated with a given repository. This is useful for scenarios where you need to verify commits or tags in a repository by accessing its cryptographic signing keys.

Practical examples include:

  • Automating verification of commit signatures in CI/CD pipelines.
  • Fetching repository signing keys to display or audit them in dashboards.
  • Integrating repository security checks into broader workflows.

Properties

Name Meaning
Owner The username or organization that owns the repository.
Repo The name of the repository to operate on.

Output

The node outputs JSON data representing the repository's signing key information. This typically includes details such as the public key used for signing commits or tags, key ID, and related metadata. The exact structure depends on the Gitea API response for the signing key endpoint.

No binary data output is indicated.

Dependencies

  • Requires an API key credential to authenticate with the Gitea server.
  • Needs the base URL of the Gitea instance configured in the credentials.
  • Depends on the Gitea REST API being accessible and properly configured to allow access to repository signing keys.

Troubleshooting

  • Authentication errors: Ensure the API key credential is valid and has sufficient permissions to access repository data.
  • Repository not found: Verify that the owner and repo names are correct and that the authenticated user has access rights.
  • API endpoint issues: Confirm that the Gitea server version supports the signing key API and that the base URL is correctly set.
  • Network errors: Check connectivity to the Gitea server and firewall settings.

Links and References

Discussion