Move branches, pull requests, and handoffs between Contrast and the repository your team already uses.
Describe the result in chat. The agent installs the integration, wires the app, and checks the connection before you ship.
What the agent sets up
One request covers the app code, provider connection, and working proof.
Connects the project to an authorized repository through the GitHub account integration.
Keeps branch work and pull request handoffs attached to the project instead of copying code between tools.
Reports missing repository access where you can reconnect it, without asking for a personal token in chat.
Values stay out of the conversation
Private values stay server-side. Stored values are resolved only by server tools. The agent receives the field name, runtime, verification status, and fix-it link, never the stored value.
GitHub uses the connected account authorization, so there is no project key to paste into chat. Reconnect repository access from the project’s GitHub settings if authorization changes.
A blocker comes with the next move
Repository access is checked through the connected GitHub account and project link. Missing installation or repository access sends you back to the GitHub connection settings instead of asking for a token.
Review GitHub access guidanceKeep the repository as the handoff
Work can move between the browser workspace, local tools, and pull request review without turning export into a one-way escape hatch.