It'd be great if you could have a running changelog in a Github issue, and then use it when creating the release… so it's created with a fully fleshed out description as soon as it's created, no manually editing after the fact.

I tested it manually using buildkite/agent#322 and buildkite/agent#32 by hitting "edit" and copy and pasting the issue description into the release description, then commenting on each issue to link to the release, and finally closing the issue.

Perhaps something like:

--link-issue "$VERSION Changelog"

And it'd just search for the first issue with that name.

i typed

go get https://github.com/buildkite/github-release

or

go install https://github.com/buildkite/github-release

are not working..

Note, my binaries are around 10MiB.

2020/05/04 00:00:14 Creating release 1.1.4-83a6f6de for repository: kami-blue/nightly-releases
2020/05/04 00:00:15 Successfully created release: "https://github.com/kami-blue/nightly-releases/releases/tag/1.1.4
-83a6f6de"

This is my output.

It says it was successful but every time I run it with a cron job, the binary upload fails, yet the tag is created. If I run my script by hand it works just fine. You can find the scripts here https://github.com/kami-blue/client/tree/master/scripts

Hi, I was wondering if you could add an option for the release description.

In the readme we could add instructions as to where to get the binary, (which is already present and uploaded as a part of releases but wasn't clear just by going through the readme).

Btw, many thanks for the tool, it was very useful!