> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/devops/pull-requests/pull-request-process/pull-request-step-1-creating.md).
# Pull Request Step 1: Creating
{% hint style="warning" %}
#### Written for the Old UI
This article was written for the old UI. The instructions are still usable, but the screenshots are outdated. In some cases, items referenced in the instructions have moved or changed. If you cannot find an item, see the [Where Did It Go](/devops/new-ui-ux-transition/where-did-it-go.md) article.
{% endhint %}
##  Overview
This article demonstrates how to start the Pull Request process by creating a Pull Request by selecting the Target and Source branches.
### Pull Request Steps
Explore our series of articles that walk you through each step of the Pull Request process. You can read them in order or select a specific article for detailed guidance on a particular stage.
* [Pull Request Step 1: Creating](/devops/pull-requests/pull-request-process/pull-request-step-1-creating.md)
* [Pull Request Step 2: Reviewing](/devops/pull-requests/pull-request-process/pull-request-step-2-reviewing.md)
* [Pull Request Step 3: Merging](/devops/pull-requests/pull-request-process/pull-request-step-3-merging.md)
## Create Pull Request
{% stepper %}
{% step %}
### Create
1. Click **Pull requests** from the left sidebar menu.
2. Click **Create pull request**.
{% endstep %}
{% step %}
### Select Branches
{% hint style="info" %}
Changes are Pulled/Merged from the **Source Branch** into the **Target Branch**.
{% endhint %}
1. Click the **Target branch** dropdown menu.
2. Select the branch to pull/merge changes into.
3. Click the **Source branch** dropdown menu.
4. Select the branch to pull/merge changes from.
{% endstep %}
{% step %}
### Add Description
1. In the **Name** textbox, enter a descriptive name for the pull request.
2. In the **Description** textbox, summarize the changes from the source branch.
3. Click **Create**.
{% endstep %}
{% step %}
### Next Step: Reviewing
After the Pull Request is created, it needs to be reviewed before merging the changes from the source branch into the target branch. Proceed to the following article for instructions on the review process.
* [Pull Request Step 2: Reviewing](/devops/pull-requests/pull-request-process/pull-request-step-2-reviewing.md)
{% endstep %}
{% endstepper %}
---
# 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.flosum.com/devops/pull-requests/pull-request-process/pull-request-step-1-creating.md?ask=&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.
