actions/forgejo-release
2
1
Fork 4
Code Issues 4 Pull requests Actions Packages Projects Releases Wiki Activity

Preserve release-notes and prerelease when using override #8

New issue
Open
opened 2024-02-20 19:41:01 +00:00 by douglasparker · 2 comments
douglasparker commented 2024-02-20 19:41:01 +00:00
Copy link

Hey,

I currently use forgejo-release to upload release artifacts to releases that I create via the UI.

The override option added in #7 makes this easier for me.

I am requesting we respect the previously set release-notes and prerelease when using the newly added override option, but only when those values are empty.

I think that gives the most flexibility. For those that want to clear out the release notes, they can for example set release-notes: ""

Hey, I currently use forgejo-release to upload release artifacts to releases that I create via the UI. The `override` option added in #7 makes this easier for me. I am requesting we respect the previously set `release-notes` and `prerelease` when using the newly added `override` option, but only when those values are empty. I think that gives the most flexibility. For those that want to clear out the release notes, they can for example set `release-notes: ""`
👍 2
earl-warren commented 2024-02-20 20:40:12 +00:00
Owner
Copy link

The way override works currently is by removing the previous release entirely and creating it from scratch. If I'm not mistaken what you suggest would be something a little different that would allow a partial modification of an existing release. This is an interesting idea, not trivial to implement though.

The way override works currently is by removing the previous release entirely and creating it from scratch. If I'm not mistaken what you suggest would be something a little different that would allow a partial modification of an existing release. This is an interesting idea, not trivial to implement though.
douglasparker commented 2024-02-20 20:49:26 +00:00
Author
Copy link

The way override works currently is by removing the previous release entirely and creating it from scratch. If I'm not mistaken what you suggest would be something a little different that would allow a partial modification of an existing release. This is an interesting idea, not trivial to implement though.

Yes, that is what I am suggesting here. 😄

> The way override works currently is by removing the previous release entirely and creating it from scratch. If I'm not mistaken what you suggest would be something a little different that would allow a partial modification of an existing release. This is an interesting idea, not trivial to implement though. Yes, that is what I am suggesting here. 😄
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
v2
v1
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: actions/forgejo-release#8
No description provided.
Delete branch "%!s()"

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?