Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node operation allows you to edit an existing milestone in a repository issue tracker. It is useful for updating milestone details such as the title, description, due date, and state (e.g., open or closed). This can help teams keep their project milestones up-to-date directly from an automated workflow without manually accessing the repository interface.

Practical examples include:

  • Automatically updating milestone deadlines based on project management tools.
  • Changing milestone states when certain conditions in your workflow are met.
  • Editing milestone descriptions to add additional context or notes programmatically.

Properties

Name Meaning
Owner The owner of the repository where the milestone exists.
Repo The name of the repository containing the milestone.
Id The identifier of the milestone to edit; can be either the milestone ID or its name.
Description (Optional) New description text for the milestone.
Due On (Optional) New due date for the milestone, typically in ISO 8601 date format.
State (Optional) New state of the milestone, e.g., "open" or "closed".
Title (Optional) New title for the milestone.

Output

The node outputs JSON data representing the updated milestone object returned by the API after editing. This includes all milestone fields such as id, title, description, due date, state, and other metadata reflecting the current state of the milestone after the update.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential to authenticate with the Gitea API.
  • The node uses the base URL configured in the credentials to send requests to the Gitea instance's API endpoint.
  • Proper permissions on the repository are necessary to edit milestones.

Troubleshooting

  • Common issues:

    • Invalid or missing repository owner or repo name will cause the API call to fail.
    • Providing an incorrect milestone ID or name will result in a "not found" error.
    • Insufficient permissions or invalid API credentials will lead to authentication errors.
    • Incorrect date format for the "Due On" field may cause validation errors.
  • Error messages and resolutions:

    • 404 Not Found: Check that the milestone ID/name, owner, and repo are correct.
    • 401 Unauthorized: Verify that the API key credential is valid and has required access.
    • 400 Bad Request: Ensure optional fields like dates and states are formatted correctly and valid.

Links and References

Discussion