Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node interacts with the Gitea API to pin an issue in a specified repository. Pinning an issue typically highlights or prioritizes it within the repository's issue tracker, making it more visible to collaborators. This operation is useful for project managers or developers who want to emphasize important issues such as critical bugs, feature requests, or tasks that require immediate attention.

Practical examples:

  • Pinning a high-priority bug report so the team can easily find and address it.
  • Highlighting a feature request during a sprint planning session.
  • Marking a task as pinned to track progress separately from other issues.

Properties

Name Meaning
Owner The username or organization name that owns the repository.
Repo The name of the repository where the issue exists.
Index The index (number) of the issue to pin within the repository's issues.

Output

The node outputs JSON data representing the result of the pinning operation on the issue. This typically includes details about the updated issue, confirming that it has been pinned successfully. The exact structure depends on the Gitea API response but generally contains issue metadata such as its ID, title, state, and pin status.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authenticating with the Gitea instance.
  • Needs the base URL of the Gitea server configured in the credentials.
  • Depends on the Gitea API being accessible and the user having permission to modify issues in the target repository.

Troubleshooting

  • Common Issues:

    • Incorrect owner or repo names may cause "not found" errors.
    • Insufficient permissions can lead to authorization errors.
    • Providing an invalid or out-of-range issue index will fail to pin the issue.
  • Error Messages:

    • 404 Not Found: Verify the repository owner and name are correct.
    • 401 Unauthorized or 403 Forbidden: Check that the API key has sufficient rights.
    • 400 Bad Request: Ensure the issue index is valid and corresponds to an existing issue.

Resolving these usually involves verifying input parameters, checking API credentials, and ensuring the user has appropriate access rights.

Links and References

Discussion