From 0619c34c253d2a47204f21a74daccbf79ae0b6f6 Mon Sep 17 00:00:00 2001 From: Stephen Meriwether Date: Sun, 18 Feb 2018 20:39:08 -0500 Subject: [PATCH] Add tag_name to update_release documentation The [edit_release](https://developer.github.com/v3/repos/releases/#edit-a-release) endpoint accepts a tag_name so that should be documented here. Furthermore, when using the `update_release` method without specifying a tag_name, the tag in Github is overwritten. For example, my tag was "v4.0" and after calling `update_release` without a tag name it became "untagged-{commit-hash}". --- lib/octokit/client/releases.rb | 1 + 1 file changed, 1 insertion(+) diff --git a/lib/octokit/client/releases.rb b/lib/octokit/client/releases.rb index 0cfdf3f99..fe41be75e 100644 --- a/lib/octokit/client/releases.rb +++ b/lib/octokit/client/releases.rb @@ -44,6 +44,7 @@ def release(url, options = {}) # Update a release # # @param url [String] URL for the release as returned from .releases + # @option options [String] :tag_name Git tag from which to create release # @option options [String] :target_commitish Specifies the commitish value that determines where the Git tag is created from. # @option options [String] :name Name for the release # @option options [String] :body Content for release notes