**Feature request: authenticated GitHub account actions for starred repositor...

Feature request: authenticated GitHub account actions for starred repositories

Copilot Chat can read a user’s public starred repositories, but it cannot use the user’s authenticated GitHub account to organize them. Please add an explicit OAuth flow that lets users grant permission for GitHub star-management actions, including:

• Creating and renaming custom star lists

• Adding or removing repositories from those lists

• Viewing private starred repositories when authorized

• Reviewing proposed changes before they are applied

• Revoking the permission from Copilot settings

Use case: I asked Copilot to categorize my starred repositories by topic, allowing overlap. It successfully retrieved my public stars and generated useful categories, but I had to apply the organization manually because the desktop app could not write to GitHub.

Suggested UX: After generating categories, show a preview such as “Create 12 lists and assign 181 repositories,” display the affected repositories, then request narrowly scoped GitHub authorization and require explicit confirmation before applying changes.

Important safeguards: Use least-privilege OAuth scopes, clearly show what permissions are requested, support dry-run previews, log the changes, and provide an undo operation where possible.

Potential API consideration: GitHub’s star-list functionality and permissions may require API support beyond basic repository access. If the API does not currently expose all required operations, this would be useful feedback for GitHub as well.

The issue identifies /chat as the entry point; begin by checking GitHub authorization and star-list API support. Done means scoped authorization, a dry-run preview and confirmation flow, private-star access where supported, permission revocation, change logging, and undo where possible, or documented API limitations.