Hyphen

GitHub Pull Request Automation

Learn how Hyphen Agent automates the creation of reviewable GitHub pull requests from supported findings and issue triggers.

Hyphen Agent can turn supported findings into reviewable GitHub pull requests. Pull request automation helps teams move from an Agent finding to a concrete code review without losing the context that produced the recommendation.

Table of Contents

Requirements

Pull request automation needs:

  • A connected GitHub integration.
  • A connected repository for the affected app.
  • Repository access for Agent to create branches and open pull requests.
  • Enough task context for Agent to identify the relevant code change.

If a repository is not connected, Agent can still surface findings where supported, but it cannot open repository pull requests.

What Can Trigger a Pull Request

Comment /hyphen on a GitHub issue in a connected repository to ask Agent to prepare a pull request. You can also use this command on existing issues from past Log Analysis runs.

When you ask manually, Agent uses the connected repository and task context it can access.

Review Workflow

Agent-created pull requests follow your normal GitHub workflow. Reviewers can inspect the diff, run checks, approve, and merge according to your repository rules. Agent does not automatically update the pull request in response to review comments.

Agent does not merge pull requests automatically as part of this workflow.

Pull Request State Updates

When a GitHub webhook reports that an Agent-created pull request was closed or reopened, Hyphen updates the matching Agent task run. The run stores the pull request state and whether GitHub reported it as merged.

If the pull request is closed without being merged, the run shows the pull request as closed and not merged. If the pull request is merged, the run records the closed state with merged set to true. Hyphen applies this update to both GitHub issue automation runs and app-specific cleanup runs that include pull request cards.

Closing a pull request does not automatically rerun Agent or merge code. Review, reopening, and merge decisions remain in GitHub and follow your repository workflow.

Results

Agent task and run views can show:

  • The repository and base branch Agent used.
  • Completed automation steps and timing.
  • Pull request cards with open, closed, or merged states.
  • Links back to the Agent task, related finding, repository, issue, and pull request.

Things to Know

  • Pull requests require GitHub to be connected for the affected app.
  • Agent proposes code changes through pull requests instead of pushing directly to production code.
  • Review, testing, and merge decisions remain with your team.