Skip to main content

Pull request

On Verify, Pull request in the header pushes the task's branch and opens GitHub's page with the title and description filled in. You create the pull request there; your agent follows its checks and comments, and you merge.

The merged pull request: its checks, its reviewers and the time from the first question to the approvalThe merged pull request: its checks, its reviewers and the time from the first question to the approval
An example task in a fictional project.

How Verify follows it​

QualityLayer finds the pull request by its branch, and the button then shows #N · open, or #N · update once the code moved. While the App is open, Verify reads checks and reviewers through gh. Without it, the task stays open until a pull or fetch brings the merge into local Git, or you mark it merged.

Your agent watches the checks​

Your agent runs qualitylayer pr watch until the checks pass:

The checks passIt checks open review threads and reads new comments, and asks you before changing anything they request.
A check failsIt reads the log, fixes the cause, pushes and watches again. It never weakens or skips a check.
The branch conflictsIt merges or rebases the way your repository does, checks that no commit was lost, then pushes.
Three attempts usedIt reports what still fails and stops.
Note
Your agent never force-pushes commits that are not its own.

When something waits for you​

Review threads and failing checks come back to you; you push the fix for review threads; you mergeOpen full size ↗ Review threads and failing checks come back to you; you push the fix for review threads; you mergeOpen full size ↗

Failing checks, review threads and conflicts appear in Needs you while the App is open. Watch pull requests can wake or resume your agent, also for new comments.

  1. Ask your agent

    "Using QL, review task retry-webhooks", with your task's name.

  2. It fixes the routine requests

    Test first, against the code and the approved Plan. Scope or design changes, and replies ready to post, come to you.

  3. Push the fix

    For review threads, the push is yours: press Push the fix. Your replies post on GitHub in your name.

When you merge​

When you merge, the task moves to Shipped with what it cost. A squash or rebase merge is recognized too; while no pull request is open, Mark as merged covers any other case. Its documents stay in docs/plans/. Further work starts with Start a follow-up.