heydeer
Sign in
Reviews on GitHub

Fix with HeyDeer

Turn review findings into a pull request you can inspect and merge. Choose what to fix, add instructions, and let HeyDeer make the changes.

Choose findingsFrom a review comment or the review page.
HeyDeer makes the changesAnd runs your tests in a sandbox.
A fix PR opensTargeting your PR’s branch.
You review and merge itThen a follow-up review checks the result.

Requirements and limits

  • The pull request is open, and its branch is in the same repository, not from a fork.
  • You have write access to the repository.
  • HeyDeer has read and write access to Contents, Pull requests, and Workflows. See GitHub App and permissions.
  • A PR has one fix running at a time, with up to 100 findings.
  • Fixes can update GitHub Actions workflow files in .github/workflows/. If HeyDeer was installed before Workflows access was requested, a GitHub App installation admin must approve the updated permissions before starting a fix.

Start a fix

  1. Select Fix with HeyDeer in a GitHub review comment, or Fix findings on the review page in HeyDeer. A link from an individual finding preselects it. Opening the page uses no credits.
  2. Choose the findings you want to address. Use Add instructions for any finding that needs extra context, such as an approach to take or behavior to preserve.
  3. Select the button that counts your selection, such as Fix 2 findings. The fix’s page shows progress and the result.
Fix findings
Findings3Select all
Retry loop never stops on a 404Highsrc/sync/retry.ts:20Edit instructionsThrow the existing HttpError so callers can log the status.
Cache key ignores the tenant IDMediumsrc/cache/keys.ts:14Add instructions
Timeout error drops the request URLLowsrc/http/client.ts:52
Fix 2 findings

The list shows open findings from all of the PR’s reviews, including earlier concerns that still need attention. Findings declined in discussion are left out.

HeyDeer can skip a selected finding that no longer applies to the code. If a fix is already running for this PR, select View fix to open it.

Review and merge the fix

HeyDeer creates a new branch and opens a PR targeting the original PR’s branch; on a PR that HeyDeer opened, it pushes to that PR’s branch instead. Read the summary and open the PR from the fix’s page to inspect the changes. You decide whether to merge them into your original PR.

To have HeyDeer push to the original PR’s branch instead, and keep fixing and reviewing until the PR is ready, use Autopilot.

The summary lists the changes, any findings HeyDeer skipped, and the tests it ran or couldn’t run. If no code changes are needed, the fix finishes without opening a PR.

After you merge the fix PR, comment @heydeer review on the original PR, or wait for its next automatic review. Opening a fix PR doesn’t resolve findings or make the HeyDeer Review check pass by itself. Follow-up reviews explains how that review rechecks earlier concerns.

Tests and CI

Starting a fix lets HeyDeer edit code, install dependencies and run your tests in an isolated sandbox with public internet access. It follows your review instructions and repository guidance such as AGENTS.md. See Security for how code execution is isolated.

Your GitHub automation may run on the fix PR. Workflows limited to a base branch such as main may run only after you merge the fix into the original PR.

Credits and cancellation

A fix uses workspace credits for the work it does, like a review. See How fixes are charged.

Someone with write access can select Cancel task while the fix is running. Canceling stops further work; commits and a fix PR it already published stay on GitHub. If credits run out, the fix stops the same way.

If the original PR changes during a fix

A fix works from the commit and branch the PR had when you started it. New commits or closing the original PR don’t cancel it, so check for conflicts before you merge.

If the original branch is deleted or renamed, HeyDeer can’t open the fix PR. Select View commit to inspect the changes and decide how to apply them.