It would be useful to me to be able to specify the content type (and ideally content-disposition) of assets uploaded as part of a release. Currently action-gh-release uses application/octet-stream for all assets, even images such as foo.png. Auto-detecting image types would be a good alternative.
For an example, see this workflow: https://github.com/garyo/sea-surface-temp-viz/blob/main/.github/workflows/make-images.yml
and on the github releases page of that repo, clicking the image filename downloads it instead of opening the image because of the content-disposition. It would be good to be able to specify that it's an image to be shown directly.
As a proof of concept, I note that there is an unmaintained action, upload-release-asset, which allows users to specify the content-type using an asset_content_type specifier.
It would be useful to me to be able to specify the content type (and ideally content-disposition) of assets uploaded as part of a release. Currently
action-gh-release
usesapplication/octet-stream
for all assets, even images such asfoo.png
. Auto-detecting image types would be a good alternative. For an example, see this workflow: https://github.com/garyo/sea-surface-temp-viz/blob/main/.github/workflows/make-images.ymlThis produces the following headers when retrieving one of the above png assets:
and on the github releases page of that repo, clicking the image filename downloads it instead of opening the image because of the
content-disposition
. It would be good to be able to specify that it's an image to be shown directly.As a proof of concept, I note that there is an unmaintained action, upload-release-asset, which allows users to specify the content-type using an
asset_content_type
specifier.