GitHub removes Copilot PR tips after Raycast ad was edited into a pull request

• Zach Manson's original post showed GitHub Copilot rewriting a pull request description after a typo-fix request, and the inserted copy promoted both Copilot and Raycast.
• According to the follow-up reporting thread, GitHub said the feature had touched more than 11,400 pull requests before it was disabled.
• In the main Hacker News discussion, practitioners framed the incident as a trust-boundary failure, not just an ugly ad.
• A fresh comment in that thread sharpened the complaint into permission abuse, arguing that GitHub mixed workflow authority with marketing.

You can read Manson's post, GitHub's quoted rollback comments in Windows Central, and the official docs for editing an existing pull request with @copilot. GitHub's own docs say Copilot can push commits directly to a PR branch, while the review docs note that a human still has to approve a Copilot-created pull request before merge in protected setups.

The ugly part was not the typo fix. It was that Copilot also rewrote the PR description with promotional copy for Raycast and GitHub's own assistant, according to Manson's account. Manson called it horrific, and that reaction landed because the edit happened inside a user-authored review artifact, not a sidebar or tooltip.

The docs already make the capability clear. In GitHub's guide to editing an existing pull request, the company says you can mention @copilot in a comment and Copilot will push commits directly to the pull request's branch.

According to Windows Central's report, GitHub product manager Tim Rogers said product tips were acceptable on Copilot-originated PRs, but became "icky" once Copilot could work on any PR by mention. The same report quoted Rogers saying the company had "disabled product tips entirely thanks to the feedback."

The secondary reporting thread says GitHub also acknowledged the feature reached more than 11,400 pull requests. That number turned a one-off screenshot into a broad product behavior.

One of the best summaries came from stratoatlas on Hacker News, who argued that write access to a PR carries an implied scope: do the delegated task, not the platform's business. A later commenter pushed the same point further, calling it textbook permission abuse because the same channel used for approvals and workflow prompts had been turned into a marketing surface.

That is the part engineers will remember. A coding agent that can edit review artifacts is already operating inside a narrow trust envelope, and this episode showed how fast that envelope tears when the edit is off-task.

GitHub's review guidance

GitHub's review docs add one useful detail that got lost in the backlash cycle. In repositories with approval requirements, the person who asked Copilot to create the pull request can approve it, but that approval does not count toward the required total, according to GitHub's review documentation.

That rule sits awkwardly next to the PR-tip incident. GitHub's workflow still assumes Copilot-authored changes need an independent human check, even as the product briefly let Copilot inject promotional text into the surrounding review surface.