Dpl: How to change GitHub release title?

[kenorb]

I've implemented deploy according to docs, but my deployments leaving _Release title_ empty:

so it fallbacks to the last commit message, which is not very user friendly for people who're visiting release pages:

Is there any way to apply/override the _Release title_?

[Joshua-Anderson]

There isn't any easy way to do this because the message would have to be stored in .travis.yml file, which would require an update before every release. I instead reccomend you create an release from the GitHub UI, which would let you input an message, or create an annotated tag, which also allows you to specify a message

[berniedurfee-ge]

If there was an option to specify the release title, I would be able to use TRAVIS_TAG, because I release on tagged releases. This would at least set the title to the tag name, which is common.

It would be nicer then just the last commit message.

[stale[bot]]

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please do feel free to either reopen this issue or open a new one. We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues

[kenorb]

I think it's still relevant.

[stale[bot]]

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please do feel free to either reopen this issue or open a new one. We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues

[kenorb]

I think it's still relevant.

[BanzaiMan]

You can pass name to the configuration. If you need a dynamic value to it, you can use environment variables available at the deployment time.

before_deploy:
  - export RELEASE_TITLE=$(date '+%Y%m%d%H%M%S')-$TRAVIS_JOB_NUMBER
deploy:
  provider: releases
  name: $RELEASE_TITLE
  ⋮ # rest

[Setheck]

I would also like to suggest, as i did in #925 that the name be defaulted to the release tag.

[BanzaiMan]

so it fallbacks to the last commit message

By the way, is this true today? When I deploy without name, I see the title is empty, but the release page shows the tag (e.g., https://github.com/BanzaiMan/travis_production_test/releases/tag/test-tag-20181115; if I go to Edit the release, I see that the title is empty.)

[Setheck]

I think GitHub does that as a UI nicety. Because if you click Edit, you will see the Title remains unset.
In my case it really just borks the Github-slack Integration because i get a notification with the title ex: Release - null but after I set the name field as you suggested in #925 I get what I wanted all along Release - Tag

[BanzaiMan]

if you click Edit, you will see the Title remains unset.

I said this. GitHub shows the tag on the Releases page if the title (set via the name parameter) is unset. This is not what @kenorb initially reported, and I wanted the confirmation.

[Setheck]

I agree, this is why I thought it was related, but I created a new issue. I wasn't seeing the same behavior

[stale[bot]]

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please do feel free to either reopen this issue or open a new one. We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues