feat: allow for draft releases #99
No reviewers
Labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
actions/forgejo-release!99
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "crueter/forgejo-release:draft"
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?
Closes #56.
Adds a
draftinput that, if true, skips the step of setting the draftstatus to false.
Signed-off-by: crueter crueter@eden-emu.dev
Well, this PR works in that it produces a new draft-release, but then the action simply fails. See https://codeberg.org/randysimons/komplete-konfigure/actions/runs/27/jobs/0/attempt/1#jobstep-7-79 (result of workflow
codeberg.org/randysimons/komplete-konfigure@63f8376107/.forgejo/workflows/release.yaml (L42))If I set
draft: false, the action succeeds - resulting in a non-draft release. See https://codeberg.org/randysimons/komplete-konfigure/actions/runs/28/jobs/0/attempt/1If
draft: true, the expression[ "$DRAFT" = "false" ] && release_draft falseresolves tofalse. Could that be the problem, and that a regularifwould fix it?The proper solution would be
[ "$DRAFT" != "false" ] || <set to draft>. I'll change that in a bitView command line instructions
Checkout
From your project repository, check out a new branch and test the changes.