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 on repositories, such as retrieving repository details. Specifically, the 'Get' operation under the 'Repository' resource fetches information about a specified repository owned by a user or organization. This is useful for scenarios where you need to programmatically access repository metadata, for example, to display repository details in a dashboard or to automate workflows based on repository attributes.
Use Case Examples
- Retrieve details of a specific repository by providing the owner and repository name.
- Use the node to fetch repository information as part of a CI/CD pipeline to verify repository settings before deployment.
Properties
| Name | Meaning |
|---|---|
| Owner | The username or organization name that owns the repository. This is required to identify the repository owner when fetching repository details. |
| Repository | The name of the repository to get information about. This is required to specify which repository's details to retrieve. |
Output
JSON
json- The JSON object containing the repository details returned from the Forgejo API.
Dependencies
- Requires an API key credential for Forgejo API authentication.
Troubleshooting
- Ensure the 'Owner' and 'Repository' fields are correctly specified; incorrect values will result in errors or no data returned.
- API authentication errors may occur if the Forgejo API credentials are missing or invalid; verify the API key and server URL configuration.
- Network issues or incorrect server URL can cause request failures; check connectivity and the configured Forgejo server URL.
Links
- Forgejo API Documentation - Official documentation for the Forgejo API, useful for understanding available endpoints and request/response formats.