Slash commands skip the commit and file the issue
The commit box now understands two slash commands. Type one and your draft becomes a labeled issue on the project's GitHub repo, credited to you, with nothing committed.
You're halfway through a complaint in the commit box when you remember you don't want to ship it. Type /bug and a space, and the box changes under your hands. A small badge appears, the placeholder asks what broke, and the Commit button becomes Open issue.
Credit goes to paulinevos, who wired the composer to GitHub. The first line of your draft becomes the title, trimmed to 256 characters, and the body tops out at 4,000. /feature adds a feature label, /bug adds a bug label, and a closing line names you as the reporter. You get five issues an hour, and only successful ones count. The site signs in as a GitHub app installed on one repository, asks for a token that can write issues there and nowhere else, then caches that token encrypted for 50 minutes.
One catch remains. Screenshots stay behind. The issue request takes text only, and once a draft has an image attached the commands go quiet, so a bug that needs a picture is still a trip to GitHub in a browser.