{"id":98569,"date":"2026-09-01T05:35:59","date_gmt":"2026-09-01T12:35:59","guid":{"rendered":"https:\/\/github.blog\/changelog\/2026-08-31-github-cli-media-in-issues-pull-requests-and-comments"},"modified":"2026-09-01T14:42:51","modified_gmt":"2026-09-01T21:42:51","slug":"github-cli-media-in-issues-pull-requests-and-comments","status":"publish","type":[3521],"link":"https:\/\/github.blog\/changelog\/2026-09-01-github-cli-media-in-issues-pull-requests-and-comments","title":{"rendered":"GitHub CLI: Media in issues, pull requests, and comments"},"content":{"rendered":"\n

GitHub CLI now has a repeatable --attach<\/code> flag that uploads a local image or video and references it inline in an issue, pull request, or comment body.<\/p>\n

This is now generally available to all users on GitHub across all plans. You just need to update gh<\/code> to v2.99.0.<\/p>\n

Why this matters?<\/span><\/a><\/h2>\n

Some things are easier to show than to describe (i.e., a UI bug, a rendered result, an error on screen). Previously, gh<\/code> only wrote text, so adding an image or video to an issue or pull request meant stopping to open the browser, drag the file into the comment box, and copy the result back. Now, gh<\/code> can attach images and videos directly from the command line.<\/p>\n

--attach<\/code> puts the image in the same command that writes Markdown. File the bug, and the screenshot lands with it, so the issue shows the actual problem the first time. Open the pull request with a before and after, and the reviewer sees the change instead of pulling the branch to check. Your coding agents get this too, so they can show a result rather than describe it.<\/p>\n

Capabilities<\/span><\/a><\/h2>\n