HTTP/2 200
server: GitHub.com
content-type: text/html; charset=utf-8
x-origin-cache: HIT
last-modified: Thu, 18 Dec 2025 15:43:44 GMT
access-control-allow-origin: *
etag: W/"69442130-16de5"
expires: Wed, 31 Dec 2025 16:54:47 GMT
cache-control: max-age=600
content-encoding: gzip
x-proxy-cache: MISS
x-github-request-id: 79AE:2B0FD4:B7BE59:CE84A9:695552FE
accept-ranges: bytes
age: 0
date: Wed, 31 Dec 2025 16:44:47 GMT
via: 1.1 varnish
x-served-by: cache-bom-vanm7210040-BOM
x-cache: MISS
x-cache-hits: 0
x-timer: S1767199487.073361,VS0,VE206
vary: Accept-Encoding
x-fastly-request-id: 551a1939c6d373ea0a047dba984c346bf2790b31
content-length: 10067
GitHub CLI | Take GitHub to the command line
CLI manual
gh release edit
Edit a release
gh release edit <tag>
Options
--discussion-category <string>
Start a discussion in the specified category when publishing a draft
--draft
Save the release as a draft instead of publishing it
--latest
Explicitly mark the release as "Latest"
-n,
--notes <string>
Release notes
-F,
--notes-file <file>
Read release notes from file (use "-" to read from standard input)
--prerelease
Mark the release as a prerelease
--tag <string>
The name of the tag
--target <branch>
Target branch or full commit SHA (default [main branch])
-t,
--title <string>
Release title
--verify-tag
Abort in case the git tag doesn't already exist in the remote repository
Options inherited from parent commands
-R,
--repo <[HOST/]OWNER/REPO>
Select another repository using the [HOST/]OWNER/REPO format
Examples
# 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
