Pull requests and merges

Review session changes and choose how they enter your repository.

Connect the project to GitHub to use hosted branch and pull-request workflows. A session’s work can be reviewed as a diff and integrated through the session controls or a requested PR workflow.

Request a reviewable change

State the target branch and review behavior in the task:

Implement CSV export on a feature branch. Run the relevant checks
and open a pull request against main. Leave the PR open for review.
Include the behavior change, verification, and any known limitations.

Review the code, check results, and preview evidence. Request corrections in the relevant session so the agent works against the right branch and context.

Merge into Main

A web session’s Merge into Main action creates a GitHub PR and merges it automatically when the change is clean. It is an integration action, so inspect the session before confirming it; the menu asks you to click again to confirm.

If conflicts occur, ask the agent in Main to resolve them, or resolve them in GitHub, then verify the result. The PR URL and session status show the outcome. Repository permissions and branch rules can prevent a merge.

Keep the checkout current

When changes land outside pre.dev, use the available Refresh from GitHub action to synchronize the hosted code. Check the selected branch and any local changes before refreshing or starting another build.

Direct agent work, sprint workflows, and session merges do not all use identical commit behavior. Specify restrictions that matter to the task and enforce branch protection in the repository where appropriate.

See GitHub connections, parallel sessions, and verification.