Skip to content

Consider using the asset description instead of the file name when publishing release assets to GitLab #128

@flelli

Description

@flelli

The use case is at #127 :

Human-readable description used as a package name, which is meant to be more like filename than description. With that limitation I cannot set nice looking asset name:

208697411-b7be5e1c-843a-4cd3-a02f-45cabf7f4553

Compare this to Nyx own release page on GH:

208697587-c6c0f2ef-0f8d-41e8-b3dc-6940083e1dee

Each release using filename for upload and description to describe that file. With description-as-a-filename I forced to label my assets just like filename, although GitLab allows to put anything I want (not kitty-0.1.1.zip, but Kitty 0.1.1 distribution for Windows for example). So I still believe that's a mistake and asset name should be used instead for package name, and asset description should be used as asset link title on GL.

Basically, if I enrich Nyx's own config to publish to GL it will fail, although it works for GH.

Consistency with other release puboishing must be checked before applying the change.

Metadata

Metadata

Assignees

Labels

type::taskShort term actionable activity.

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions