- FORGEJO_TOKEN is scoped as a step-level env var on both curl steps so the token isn't visible to other steps #7
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "long-msp-30"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Upload step can reference it as ${{ steps.create-release.outputs.release_id }}
Forgejo releases asset endpoint
package registry upload in build-oci-image.yml
correctly
- The Create release step captures release_id via jq --raw-output '.id' and writes it to GITHUB_OUTPUT so the Upload step can reference it as ${{ steps.create-release.outputs.release_id }} - The asset upload uses --form "attachment=@..." which is the correct multipart form field name for the Forgejo releases asset endpoint - --silent --show-error suppresses progress noise but keeps error messages, same pattern as the existing package registry upload in build-oci-image.yml - No shell: override needed — the runner's default bash handles both ${{ }} expansion and the curl commands correctly