Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node interacts with the Gitea API to unpin a specific issue in a repository. Pinning issues is a way to highlight important or frequently referenced issues at the top of the issue list. The "Unpin Issue" operation removes this highlight, returning the issue to its normal position in the list.

Common scenarios for using this node include:

  • Managing issue visibility by programmatically unpinning issues that are no longer relevant or resolved.
  • Automating repository maintenance workflows where pinned issues need to be rotated or updated.
  • Integrating with other automation tools to keep issue boards organized without manual intervention.

For example, after resolving a critical bug that was pinned for attention, you can use this node to unpin the issue automatically as part of your deployment pipeline.

Properties

Name Meaning
Owner The owner (user or organization) of the repository containing the issue.
Repo The name of the repository where the issue exists.
Index The index (position) of the issue to unpin within the pinned issues list.

Output

The node outputs JSON data representing the result of the unpin operation. This typically includes confirmation details such as the updated state of the issue or a success message from the API. No binary data output is involved.

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 sufficient permissions to modify issues in the specified repository.

Troubleshooting

  • Issue Not Found or Invalid Index: If the provided index does not correspond to a pinned issue, the API may return an error. Verify the index value matches an existing pinned issue.
  • Authentication Errors: Ensure the API key credential is valid and has appropriate permissions.
  • Repository or Owner Incorrect: Double-check the spelling and case sensitivity of the owner and repo names.
  • API Connectivity Issues: Confirm the Gitea server URL is correct and reachable from n8n.

Links and References

Discussion