Cannot disable release body append mechanism when updating an existing release about action-gh-release

[softprops]

That seems doable, yes

Some projects need to be built on multiple architectures and multiple operating systems. For example, compile on x64-windows, x86-windows, x64-linux, x64-osx. Such project is run on 4 different jobs, uses a matrix configuration -> each job creates a release with a unique artifact.

A few alternatives that require no change to to this action

• You could leverage upload and download artifacts actions. Have multiple jobs that build release artifacts use upload-artifact then in a separate job that depends on those, download the artifacts and run the gh release action just once

• use an if filter to conditionally set release notes for one of your architectures assuming all release notes are the same and an flipped if for the remainder

[matusnovak]

[...] then in a separate job that depends on those, download the artifacts and run the gh release action just once

That sounds like a good idea. Thanks!

[softprops]

you bet. let me know if you need help on how to structure that

[abcfy2]

Any update? I really need this feature.

[orhun]

I totally agree. This feature would be great.

[movermeyer]

@abcfy2 @orhun

The original use case mentioned in this issue is solved by the upload / download pattern.

Is there another motivating use case for this feature?

[orhun]

@abcfy2 @orhun

The original use case mentioned in this issue is solved by the upload / download pattern.

Is there another motivating use case for this feature?

Thanks for letting me know. Honestly, I don't remember what I was trying to do at that time (almost a year ago) so I don't really know 🙈

[robkooper]

My use case is that my artifacts are large (100Mb - 200Mb each). Having 3 of them will get me over my free 500Mb limit when using upload/download artifacts.

I will use the if statement approach to create release-notes only for one build.