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. This task is automatically used when an issue created by the Log Analysis task is tagged with the comment /hyphen.
Table of Contents
- Requirements
- What Can Trigger a Pull Request
- Review Workflow
- Pull Request State Updates
- Results
- Things to Know
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
Agent can open pull requests from supported task findings, including:
- Log analysis findings where Agent identifies an actionable code fix.
- Any time Agent is tagged in a GitHub issue comment.
The pull request includes context from the Agent task and run so reviewers can understand why Agent proposed the change.
If you have the Hyphen Agent installed in your GitHub organization, you can comment /hyphen on an issue to ask it to prepare a pull request to address that issue.
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.
- Log analysis may create or comment on issues before a pull request is opened.
- Review, testing, and merge decisions remain with your team.