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 manage repositories. Specifically, the 'Delete' operation under the 'Repository' resource allows users to delete a specified repository owned by a user or organization. This is useful for automating repository cleanup or management tasks within workflows.
Use Case Examples
- Deleting a repository when a project is archived or no longer needed.
- Automating repository deletion as part of a larger DevOps pipeline.
Properties
| Name | Meaning |
|---|---|
| Owner | The username or organization name that owns the repository to be deleted. |
| Repository | The name of the repository to delete. |
Output
JSON
json- The JSON response from the Forgejo API after attempting to delete the repository. Typically indicates success or failure of the deletion operation.
Dependencies
- Requires an API key credential for Forgejo API authentication.
Troubleshooting
- Common issues include providing incorrect owner or repository names, which will result in API errors indicating the repository was not found.
- Insufficient permissions or authentication errors if the API key does not have rights to delete the repository.
- Network or server errors from the Forgejo API endpoint.
Links
- Forgejo API Documentation - Official API documentation for Forgejo, useful for understanding the API endpoints and required parameters.