Actions73
- Repository Actions
- Issue Actions
- Pull Request Actions
- User Actions
- Organization Actions
- Release Actions
- Webhook Actions
- Branch Actions
- Commit Actions
- Tag Actions
Overview
This node interacts with the Forgejo API to perform various operations related to issues within repositories. Specifically, the 'Search' operation under the 'Issue' resource allows users to search for issues across repositories using a query string. It supports pagination options to control the number of results and the page to start from. This node is useful for automating issue tracking, filtering issues based on specific criteria, and integrating issue search functionality into workflows.
Use Case Examples
- Search for issues containing specific keywords or phrases across multiple repositories.
- Retrieve a paginated list of issues matching a search query to analyze or report on issue trends.
Properties
| Name | Meaning |
|---|---|
| Query | The search query string used to find matching issues. |
| Additional Options | Optional parameters to control pagination, including the page number to start from and the maximum number of results per page. |
Output
JSON
json- The JSON response containing the search results for issues. This can be an array of issue objects or a single object depending on the API response.
Dependencies
- Requires an API key credential for Forgejo API authentication.
Troubleshooting
- Ensure the 'query' parameter is not empty as it is required for searching issues.
- Check API credentials and server URL configuration to avoid authentication errors.
- Pagination parameters 'page' and 'limit' should be within valid ranges to prevent request errors.
- Handle API rate limits or network issues that may cause request failures.
Links
- Forgejo API Documentation - Official API documentation for Forgejo, including endpoints for searching issues.