GiteaInstall

Overview

This node interacts with the Gitea API to move the position of a pinned issue within a repository. It allows users to reorder pinned issues by specifying the current index of the issue and the new desired position. This is useful for project management workflows where prioritizing or organizing pinned issues visually in a repository's issue tracker is needed.

Practical examples include:

• Reordering pinned issues to reflect changing priorities.
• Organizing issues for sprint planning or release milestones.
• Adjusting the display order of important issues on a repository homepage.

Properties

Output

The node outputs JSON data representing the result of the move operation. Typically, this will include confirmation of the updated pin positions or the updated issue data reflecting its new position. There is no indication that binary data is output by this node.

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 REST API endpoint for moving pinned issues.

Troubleshooting

• Common Issues:

  • Incorrect repository owner or repo name can cause "not found" errors.
  • Providing invalid index or position values (e.g., out of range) may lead to API errors.
  • Authentication failures if the API key or URL is misconfigured.

• Error Messages:

  • "404 Not Found": Check that the owner and repo names are correct and that the issue index exists.
  • "401 Unauthorized": Verify that the API key credential is valid and has sufficient permissions.
  • "400 Bad Request": Ensure that the index and position parameters are valid integers within allowed ranges.

Links and References

• Gitea API Documentation
• Gitea Official Website