> 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/create-a-project-pull-request.md).

# Create a project pull request

A change request submits a workflow version for review before release. Include a description of the changes so a reviewer can assess them.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2FlzYIEpViwtrz2Zdlsncb%2FG071.mp4?alt=media&token=d68fb73b-440a-4854-bc12-0c194d5b1c48>" %}

## Before you start

Agree on the target project or stage and identify a reviewer before submitting. If you need to configure required approvals, use [Deployments and approval requirements](https://docs.stackai.com/guides-and-quickstarts/releases-and-environments/deployments-and-approval-requirements.md). Describe the user-visible outcome and include one test input with its expected result, so the reviewer can reproduce the check.

Your organization must use an approval process for workflow releases.

## Check the proposed workflow

Run the candidate draft and inspect its output.

![Candidate draft test result](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/xLtexIGeatxHeYOPljit/assets/g071-g071-01-result.png)

Resolve known problems before submitting it for review.

Open Publish and Review changes.

![Review changes comparison](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/IYYWQcpolDxLBuPuD9iv/assets/g071-g071-02-diff.png)

Confirm that the displayed differences match the change you intend to request.

## Submit a change request

Open Create Pull Request, choose the target project, and describe the change.

![Pull request target and description form](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/aj4XMv3r4AhyEpHFX70R/assets/g071-g071-03-form.png)

Include the expected behavior and the checks that support it.

Submit the request and locate it in Pending.

![Pending request after submission](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/HTdaUxctI120AU6ILBl0/assets/g071-g071-04-pending.png)

Open View drafted changes to confirm the saved description and proposed configuration.

## Important behavior

A pending change request is not a published release. A reviewer must complete the required approval process.


---

# 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/create-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.
