281 Search results for "diff context"

Skillsets and agents are the two ways to extend Copilot's capabilities and context through the Copilot Extensibility Platform. They let you integrate external

from the user is pre-processed by the Copilot Chat system, combined with contextual information (for example, the name of the repository the user is currently

directly into your development workflow, allowing you to prompt models without context switching. Using AI models in Copilot Chat If you have a Copilot subscription

resources from GitHub with your Copilot agent. Context passing for your agent Learn how to use context passing with your Copilot agent. Using Copilot's

preventing data sharing across extensions. The data retention period for thread context is 30 days. Any additional organization and repository data that is authorized

from the user is pre-processed by the Copilot Chat system, combined with contextual information (for example, the current date and time and the name of the

high level summary of what happened with the build. Statuses can include a context to indicate what service is providing that status. For example, you may

approvals when commits are pushed that affect the diff in the pull request. GitHub records the state of the diff at the point when a pull request is approved

file's name in the "GitHub Pull Request" side bar. This displays a diff view in the editor, with the version of the file from the base branch on

list to open the file in the Workspace editor. The file is displayed in a diff view. You can change the view if required. See Changing the Workspace options