GH-RELEASE-EDIT(1) GitHub CLI manual GH-RELEASE-EDIT(1)

# [NAME](#NAME)

gh-release-edit - Edit a release

# [SYNOPSIS](#SYNOPSIS)

**gh release edit <tag>**

# [OPTIONS](#OPTIONS)

[**--discussion-category** **<string>**](#discussion_category)

Start a discussion in the specified category when publishing a draft

[**--draft**](#draft)

Save the release as a draft instead of publishing it

[**--latest**](#latest)

Explicitly mark the release as "Latest"

[**-n**, **--notes** **<string>**](#n)

Release notes

[**-F**, **--notes-file** **<file>**](#F)

Read release notes from file (use "-" to read from standard input)

[**--prerelease**](#prerelease)

Mark the release as a prerelease

[**--tag** **<string>**](#tag)

The name of the tag

[**--target** **<branch>**](#target)

Target branch or full commit SHA (default \[main branch])

[**-t**, **--title** **<string>**](#t)

Release title

[**--verify-tag**](#verify_tag)

Abort in case the git tag doesn't already exist in the remote repository

# [OPTIONS INHERITED FROM PARENT COMMANDS](#OPTIONS_INHERITED_FROM_PARENT_COMMANDS)

[**-R**, **--repo** **<\[HOST/\]OWNER/REPO>**](#R)

Select another repository using the \[HOST/]OWNER/REPO format

# [EXIT CODES](#EXIT_CODES)

0: Successful execution

1: Error

2: Command canceled

4: Authentication required

NOTE: Specific commands may have additional exit codes. Refer to the command's help for more information.

# [EXAMPLE](#EXAMPLE)

```
# Publish a release that was previously a draft
$ gh release edit v1.0 --draft=false
# Update the release notes from the content of a file
$ gh release edit v1.0 --notes-file /path/to/release_notes.md
```

# [SEE ALSO](#SEE_ALSO)

[**gh-release(1)**](/man/os/gh/gh-release.1)

Sep 2026

---

Document: gh-release-edit(1) from gh 2.101.0-r1 (Chainguard OS)
Source: https://github.com/cli/cli