- Two steps collapsed into one — RELEASE_ID is a plain shell variable in the same process, never touching #8
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?
GITHUB_OUTPUT. This eliminates the most likely failure: Forgejo runner not setting GITHUB_OUTPUT, or the
step-output read returning empty and silently posting to a bad URL.
consistently across both curl calls as ${TAG}. Cleaner than mixing template expressions and shell variables in
a single command.
unexpected), this will print null visibly in the log before the upload curl fails with a 404, making the root
cause obvious.
GITHUB_OUTPUT. This eliminates the most likely failure: Forgejo runner not setting GITHUB_OUTPUT, or the step-output read returning empty and silently posting to a bad URL. - TAG passed as an env var — ${{ forgejo.ref_name }} is expanded once at the YAML level into TAG, then used consistently across both curl calls as ${TAG}. Cleaner than mixing template expressions and shell variables in a single command. - echo "Created release ID: ${RELEASE_ID}" added — if jq returns null (meaning the create-release response was unexpected), this will print null visibly in the log before the upload curl fails with a 404, making the root cause obvious.