Actions73
- Repository Actions
- Issue Actions
- Pull Request Actions
- User Actions
- Organization Actions
- Release Actions
- Webhook Actions
- Branch Actions
- Tag Actions
- Commit Actions
Issue → Get
AI-generatedOverview
This node interacts with the Forgejo API to perform various operations on issues within repositories. Specifically, for the 'Issue' resource and 'Get' operation, it retrieves detailed information about a specific issue identified by its issue number within a given repository owned by a specified user or organization. This is useful for workflows that need to fetch issue details for tracking, reporting, or automation purposes.
Use Case Examples
- Retrieve details of a specific issue by providing the repository owner, repository name, and issue number.
- Use in automation to fetch issue data and trigger subsequent actions based on issue status or content.
Properties
| Name | Meaning |
|---|---|
| Owner | The username or organization that owns the repository containing the issue. |
| Repository | The name of the repository where the issue exists. |
| Issue Number | The unique number identifying the issue within the repository. |
Output
JSON
json- The JSON object containing the detailed information of the retrieved issue, including its title, body, labels, assignees, state, and other metadata.
Dependencies
- Forgejo API authentication credentials (API key or token)
Troubleshooting
- Ensure that the provided owner, repository, and issue number are correct and that the issue exists.
- Check that the Forgejo API credentials are valid and have sufficient permissions to access the repository and issue.
- Common errors include 404 Not Found if the issue does not exist or 401 Unauthorized if authentication fails.
Links
- Forgejo API Documentation - Official API documentation for Forgejo, useful for understanding available endpoints and data structures.