GiteaInstall

Overview

This node interacts with the Gitea API to manage issues within repositories. Specifically, the "Issue Delete Stop Watch" operation stops and deletes a stopwatch timer associated with a particular issue in a repository. This can be useful for tracking time spent on issues and then stopping that tracking when work is complete or paused.

Practical scenarios include:

• Developers or project managers who want to track time spent on specific issues and stop the timer once the task is done.
• Automation workflows where timing data needs to be programmatically controlled or reset.

Properties

Output

The node outputs JSON data representing the result of the stopwatch deletion operation on the specified issue. This typically includes confirmation of the stopwatch being stopped and deleted, or details about the affected issue's timing state.

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 appropriate permissions to modify issues and their timers.

Troubleshooting

• Common Issues:

  • Incorrect repository owner or name may cause "not found" errors.
  • Providing an invalid issue index could lead to failure in locating the issue.
  • Insufficient permissions might result in authorization errors.
  • Network connectivity problems to the Gitea server will prevent API calls.

• Error Messages:

  • 404 Not Found: Check if the owner, repo, and issue index are correct.
  • 401 Unauthorized: Verify that the API key credential is valid and has necessary scopes.
  • 500 Internal Server Error: Could indicate server-side issues; retry later or check server logs.

Links and References

• Gitea API Documentation
• n8n Documentation on Creating Custom Nodes