Skip to content

Latest commit

 

History

History
51 lines (35 loc) · 3.34 KB

pull-request.mdx

File metadata and controls

51 lines (35 loc) · 3.34 KB
title Pull request
description Push the change and open GitHub's pull request page from Verify, then follow its checks and reviewers until you merge it.
mdx
format
mdx

import { Card, CardGroup, Steps, Step, Note, Screenshot, NextSteps } from "@site/src/components/kit";

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.

How Verify follows it {#following}

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 {#watch}

Your agent runs qualitylayer pr watch until the checks pass:

It checks open review threads and reads new comments, and asks you before changing anything they request. It reads the log, fixes the cause, pushes and watches again. It never weakens or skips a check. It merges or rebases the way your repository does, checks that no commit was lost, then pushes. It reports what still fails and stops.

Your agent never force-pushes commits that are not its own.

When something waits for you {#waits}

Review threads and failing checks come back to you; you push the fix for review threads; you merge Review threads and failing checks come back to you; you push the fix for review threads; you merge

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.

"Using QL, review task retry-webhooks", with your task's name. Test first, against the code and the approved Plan. Scope or design changes, and replies ready to post, come to you. For review threads, the push is yours: press **Push the fix**. Your replies post on GitHub in your name.

When you merge {#merged}

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.

<NextSteps items={[ { title: "Verify", href: "/docs/steps/verify", text: "The checks and your review before the pull request." }, { title: "Settings", href: "/docs/reference/settings#git-and-editor", text: "Watch pull requests and Git defaults." }, ]} />