> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/guides-and-quickstarts/releases-and-environments/review-a-project-pull-request.md).

# Review a project pull request

Review a change request to decide whether a workflow version is ready for release. Inspect the changes and run the proposed workflow before you approve it.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2Fk10e5Ss9qZ1wI8aV0sgr%2FG072.mp4?alt=media&token=ea2eb3c3-2c7e-4f45-b4e7-b1233986a33a>" %}

## Before you start

Ask the author to include the expected behavior, test inputs, and target project or stage. Use [Project version history and diffs](https://docs.stackai.com/guides-and-quickstarts/releases-and-environments/project-version-history-and-diffs.md) to read the comparison, and involve the workflow builder if you cannot explain a changed node or connection before approving it.

You need permission to approve the change request.

## Inspect the proposed changes

Open a pending request and select View drafted changes.

![Proposed node changes](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/i5n45Ns0aG4GQ7Oi7lnX/assets/g072-g072-01-nodes.png)

Read the description and inspect the node changes before making a decision.

Select Edges to review connection changes separately.

![Proposed edge changes](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/CWuc8Lu6vuOHoYeSbbzX/assets/g072-g072-02-edges.png)

Check whether the proposed wiring changes the path taken by inputs or outputs.

## Approve the request

Select Approve pull request and read the confirmation.

![Pull request approval confirmation](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/Kp6XTi6pqhZVtyy2YMTD/assets/g072-g072-03-confirmation.png)

Approval can replace the published version, so verify the target and complete change before confirming.

## Verify the release

Open Approved after the decision completes and locate the request.

![Approved request history](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/Wi8xcnHRrWZobVwrkP9X/assets/g072-g072-04-approved.png)

Confirm its status and reviewer information in the saved history.

Open the published interface in a fresh conversation and submit a representative request.

![Released interface response](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/7uCm6p2sZfEdeDeb4Cd4/assets/g072-g072-05-live-result.png)

Verify the released behavior from the actual response.

## Test the candidate and send back an unsafe change

Open the request's review workspace from **View drafted changes** or **Review**, then run representative input there and inspect Output. Check that you are testing the request's proposed version rather than the current editor draft. For a staged release, open **Deployments → View PRs → Review**; the fuller stage-specific procedure is in [Deployments and approval requirements](https://docs.stackai.com/guides-and-quickstarts/releases-and-environments/deployments-and-approval-requirements.md).

Before deciding, review changed instructions, nodes, connections, configuration references, and the intended target. Record the test input, expected behavior, and observed result in a request comment so the author can reproduce any problem.

If the candidate is not ready, submit the comment and choose **Reject Changes** in the review panel. Verify the request appears as Rejected. A comment alone does not reject it. The author should correct the working draft, rerun the checks, and submit a new request for the intended version and target. Do not approve a request merely to unblock that correction cycle.

If the live check fails after approval, record the affected stage and version. For staged deployments, follow the **Recover a stage after a failed release** steps in [Deployments and approval requirements](https://docs.stackai.com/guides-and-quickstarts/releases-and-environments/deployments-and-approval-requirements.md). For a project without staged deployment, prepare and test a corrective draft and publish it through its normal approval process. If access must stop while the problem is resolved, an authorized owner can deliberately unpublish the interface using [Publish and unpublish a project](https://docs.stackai.com/guides-and-quickstarts/releases-and-environments/publish-and-unpublish-a-project.md); this creates downtime.

## Important behavior

Approval can replace the published workflow version. Check the target stage and proposed changes before you approve.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/guides-and-quickstarts/releases-and-environments/review-a-project-pull-request.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
