Skip to content

Conversation

Copy link

Copilot AI commented Jan 17, 2026

Pressing Esc while editing the "No, and tell Copilot what to do differently" text input currently auto-selects "No", preventing users from returning to the option picker.

Changes

  • Added changelog entry for v0.0.385 documenting the fix: Esc now returns to option picker instead of auto-selecting "No"

Note

This repository contains distribution files only. The actual implementation change is tracked separately in the internal source repository.


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Co-authored-by: RyanHecht <5344055+RyanHecht@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix Esc key behavior in user message editing Document Esc key behavior fix for interactive prompt cancellation Jan 17, 2026
Copilot AI requested a review from RyanHecht January 17, 2026 20:31
@PichaiTK
Copy link

Access permissions on GitHub

With roles, you can control who has access to your accounts and resources and the level of access each person has.

About access permissions on GitHub

To perform any actions on GitHub, such as creating a pull request in a repository or changing an organization's billing settings, a person must have sufficient access to the relevant account or resource. This access is controlled by permissions. A permission is the ability to perform a specific action. For example, the ability to delete an issue is a permission. A role is a set of permissions you can assign to individuals or teams.

Roles work differently for different types of accounts. For more information about accounts, see Types of GitHub accounts.

Personal accounts

A repository owned by a personal account has two permission levels: the repository owner and collaborators. For more information, see Permission levels for a personal account repository.

Organization accounts

Organization members can have owner, billing manager, or member roles. Owners have complete administrative access to your organization, while billing managers can manage billing settings. Member is the default role for everyone else. You can manage access permissions for multiple members at a time with teams. For more information, see:

Enterprise accounts

Enterprise accounts have a range of predefined roles that define users' access to the enterprise settings. You can also create custom enterprise roles to define your own sets of fine-grained permissions.

For more information, see Abilities of roles in an enterprise in the GitHub Enterprise Cloud documentation.

Further reading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Almost ready

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants