Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node operation allows you to create a new milestone for an issue in a specified repository on a Gitea instance. Milestones help organize and track progress on issues by grouping them under specific goals or deadlines. This operation is useful when managing project timelines, planning releases, or categorizing issues by stages.

Practical examples:

  • Creating a milestone named "Version 1.0" with a due date to track all issues targeted for the first release.
  • Setting a milestone state to "closed" once the related issues are resolved and the milestone is complete.

Properties

Name Meaning
Owner The owner (user or organization) of the repository where the milestone will be created.
Repo The name of the repository in which to create the milestone.
Description Optional text describing the milestone’s purpose or details.
Due On Optional due date for the milestone, typically in ISO 8601 date format (e.g., YYYY-MM-DD).
State The state of the milestone; can be either "Open" or "Closed".
Title The title or name of the milestone.

Output

The node outputs JSON data representing the newly created milestone object as returned by the Gitea API. This includes fields such as milestone ID, title, description, state, due date, creation timestamps, and other metadata related to the milestone.

No binary data output is involved in this operation.

Dependencies

  • Requires connection to a Gitea instance via its REST API.
  • Needs an API authentication token credential configured in n8n to authorize requests.
  • The base URL for the Gitea API must be set in the credentials configuration.

Troubleshooting

  • Common issues:

    • Invalid or missing repository owner or name will cause the API call to fail.
    • Incorrect or expired API authentication token will result in authorization errors.
    • Providing an invalid date format for "Due On" may cause request rejection.
    • Attempting to create a milestone with a duplicate title might be rejected depending on the Gitea server settings.
  • Error messages:

    • 401 Unauthorized: Check that the API token is valid and has sufficient permissions.
    • 404 Not Found: Verify that the owner and repo names are correct and accessible.
    • 400 Bad Request: Ensure all required fields are provided and correctly formatted, especially dates.

Resolving these usually involves verifying input parameters, checking API credentials, and confirming repository access rights.

Links and References

Discussion