Forgejo icon

Forgejo

Interact with Forgejo API
Join our community

Actions73

Overview

This node operation uploads an asset file to a specific release in a Forgejo repository. It is useful for automating the process of attaching binary or other asset files to a release, such as compiled binaries, documentation, or other release-related files. For example, after creating a release, you can use this operation to upload a compiled executable or a zip archive as an asset to that release.

Use Case Examples

  1. Uploading a compiled application binary to a release for distribution.
  2. Attaching a zip file containing documentation or additional resources to a release.

Properties

Name Meaning
Owner The username or organization that owns the repository where the release exists.
Repository The name of the repository where the release exists.
Release ID The unique identifier of the release to which the asset will be uploaded.
Asset Name The name to assign to the uploaded asset file.
Asset File Path The local file path of the asset file to upload.

Output

JSON

  • json - The JSON response from the Forgejo API representing the uploaded asset details.

Dependencies

  • Requires an API key credential for Forgejo API authentication.

Troubleshooting

  • Ensure the Release ID is correct and corresponds to an existing release in the specified repository.
  • Verify that the Asset File Path points to a valid and accessible file on the local filesystem.
  • Check that the API credentials have sufficient permissions to upload assets to the repository release.
  • Common errors include authentication failures, file not found errors, and invalid release ID errors. Resolving these involves verifying credentials, file paths, and release existence.

Links

Discussion