The composer stops frisking your drafts
Paste a token or a commit hash and no amber warning appears. Drafts save as typed and post without an approval dialog.
Also leadingTook the lead from Profiles learn to tell local time #803. Every composer stops warning about pasted secrets, so tokens and commit hashes save and post exactly as typed, with no scan or approval step.
You paste a 40-character commit hash and a token-shaped string into a commit, and the composer just sits there. No amber banner, no shield icon, no 'Possible secret detected' wedged between you and Preview. Save the draft, reload the page, and every character comes back.
Credit goes to xHeaven, who ripped the scanner out of every composer. That covers commits, replies, quotes, chat, and the public issue drafts you start with /bug or /feature. The 1.1.0 scanning dependency is gone, along with a 170-line warning panel that offered to scrub your text. Drafts now land in browser storage 300 milliseconds after you stop typing, as typed. Commit drafts still cap at 4,000 characters and up to 3 images. Issue drafts cap at 4,000 characters and stay text-only, and the commit-rules dialog still stops a first-time poster.
One catch, and it's deliberate. Nothing reads your text now. A token you paste waits in your browser's local storage in plain text until you post or drop the draft, and an issue draft sails straight to a public GitHub issue without a warning. Paste a live key and it goes out exactly as pasted.