GiteaInstall

Overview

This node interacts with the Gitea API to manage issues within repositories. Specifically, the "Issue Start Stop Watch" operation allows users to start or stop a stopwatch on a particular issue by its index in a repository. This can be useful for tracking time spent on specific issues directly from an automation workflow.

Practical examples include:

• Automatically starting a timer when work begins on an issue.
• Stopping the timer once work is completed or paused.
• Integrating time tracking into project management workflows without manual intervention.

Properties

Output

The node outputs JSON data representing the result of the stopwatch action on the specified issue. This typically includes details about the issue and the updated stopwatch status (e.g., whether the stopwatch was started or stopped, timestamps, and any related metadata).

No binary data output is indicated.

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 being accessible and properly configured to allow stopwatch operations on issues.

Troubleshooting

• Common Issues:

  • Incorrect repository owner or repo name may cause "not found" errors.
  • Invalid issue index could lead to errors if the issue does not exist.
  • Authentication failures if the API key or URL is misconfigured.
  • Network connectivity problems to the Gitea server.

• Error Messages:

  • "Issue not found": Verify the owner, repo, and issue index values.
  • "Authentication failed": Check that the API key credential and base URL are correct.
  • "API request failed": Ensure the Gitea server is reachable and the API endpoint supports stopwatch operations.

Links and References

• Gitea API Documentation — Official API docs for reference on issue and stopwatch endpoints.
• n8n Documentation — For general guidance on using credentials and configuring HTTP request nodes.