Pull requests from Perfloop.

For the person who reviews a pull request Perfloop opened: how to ask for a change, what Perfloop does by itself, and what you can change yourself.

Ask for a change

There are no commands. Comment, suggest a change, or submit a review in plain words, as you would for any contributor. Perfloop reads them and either answers on the pull request or pushes a new commit to it. It does not open a second pull request.

When Perfloop starts work on your comment, it adds 👀 to it. A comment from someone who can push to the repository can start work at once. Other comments, and some answers, wait until the workspace that opened the pull request approves them.

To have this pull request rebased on the current target branch, ask in a comment. Perfloop rebases it even when it still merges cleanly.

What Perfloop does by itself

• When a check fails, Perfloop works on a fix and pushes it to this pull request.

• When the pull request no longer merges cleanly, Perfloop rebuilds the change on the current target branch and updates this pull request.

• Perfloop never approves or merges.

Change it yourself

When the branch is in a fork that Perfloop owns, GitHub does not let you push to it. Use a suggested change in a review instead, or merge and follow up with your own commit. When the branch is in your own repository, you can push to it, and Perfloop never overwrites a head you changed.

To stop Perfloop's work on a pull request, close it.

The Case and evidence link opens the Case behind the pull request. If the repository reserves the description for a commit message or forbids Markdown or product trailers there, Perfloop leaves out this link and its attribution. When a private workspace opened the pull request, only members of that workspace can open its Case.

Also in this section: Quickstart, Performance, Bugs, Security, The loop, Case states, Steering and learning, Initiatives, Autonomy and limits, Members, The MCP server, and Events.

Questions: hello@perfloop.ai