When creating a new release if you leave the title blank the site defaults it to the tag value, but the slack notification doesn't do the same so all it says is Release -.

If I go back and edit this release the title is blank which I guess is why the notification doesn't contain a value.
The release in question: https://github.com/xt0rted/AppVeyor-Dark/releases/tag/v1.0.4
Is this still relevant? If so, just comment with any updates and we'll leave it open. Otherwise, if there is no further activity, it will be closed.
Still happening
Is this still relevant? If so, just comment with any updates and we'll leave it open. Otherwise, if there is no further activity, it will be closed.
Just tested this and it's still happening.
This is still happening on 2019-10-15. In my case I get a notification with text Release- null. And the use-case is Travis-CI deploying a release on a successful build.

As you can see from the screenshot there is a tag and even Travis knows about it.
And apparently there even was a pull request with a fix (#706), which the author closed himself, as nobody took a look at it in half a year :/
Is this still relevant? If so, just comment with any updates and we'll leave it open. Otherwise, if there is no further activity, it will be closed.
Still happening.
Facing the same issue. Is there a workaround for this until a fix is ready?
@kshitizdange the only workaround I know of is to provide a value for the title instead of letting the site set it automatically.
If this is still active, would like to help.
Most helpful comment
This is still happening on 2019-10-15. In my case I get a notification with text

Release- null. And the use-case is Travis-CI deploying a release on a successful build.As you can see from the screenshot there is a tag and even Travis knows about it.
And apparently there even was a pull request with a fix (#706), which the author closed himself, as nobody took a look at it in half a year :/