> 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/overview-of-pull-requests.md).

# Overview of Pull Requests

{% 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 %}

## ![](https://1800549522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRpUu5iMlzMFAudyBvMOl%2Fuploads%2FG5ZbxX918xOHwbAwAJ4n%2FSummary2-Small-Icon.svg?alt=media\&token=da26a67f-ff7f-47b3-8669-06be960dc2d7) Overview

Pull Requests are a key part of the Cloud DevOps workflow, enabling updates from a source branch to a target branch. They are designed to support collaboration through code reviews that must be approved before merging.

**Benefits of Pull Requests:**

* **Code Review**: Enables thorough examination of changes before merging.
* **Conflict Detection**: Identifies and addresses conflicts early in the process.
* **Clean Release History**: Maintains an organized and clear project history.

{% hint style="info" %}

#### Smart Merge vs Pull Request

Smart Merge and Pull Request both merge changes from a source branch into a target branch, but each suits a different workflow.

**Smart Merge** is a streamlined, single-step process that merges changes directly between branches without requiring a Pull Request or team approval. It works well for time-sensitive situations, such as urgent fixes or critical changes that need to ship quickly.

A **Pull Request**, by contrast, is a structured, multi-step process built for team collaboration. It lets multiple reviewers inspect the changes, request revisions, and formally approve them before merging.

As a general rule, use a Pull Request when changes need oversight or sign-off from other team members, and choose Smart Merge when you need to integrate changes quickly.
{% endhint %}

To learn about Smart Merge, see the following article.

* [Using Smart Merge](/devops/code/branch-actions/using-smart-merge.md)

## Pull Request Overview Page <a href="#pull-request-overview-page" id="pull-request-overview-page"></a>

The Pull Request overview page provides a comprehensive snapshot of all active requests. Serving as the central hub, it facilitates progress tracking and merge readiness. Each Pull Request displays the following details.

{% hint style="info" %}

#### Active Pull Requests

The Pull Request Overview page only lists active Pull Requests. Once a Pull Request is **Merged** or **Closed**, it is removed from the active Pull Requests list.
{% endhint %}

<table data-header-hidden><thead><tr><th width="179.333251953125"></th><th></th></tr></thead><tbody><tr><td>Title and ID</td><td>The Pull Request title and ID number. Each Pull Request is assigned a unique sequential ID number.</td></tr><tr><td>Status</td><td>The status of the Pull Request can be one of the following: Created, Review Requested, Changes Requested, and Approved.</td></tr><tr><td>Author</td><td>The Flosum User who created the Pull Request.</td></tr><tr><td>Latest Activity</td><td>The amount of time since the latest activity for the Pull Request.</td></tr><tr><td>Target and Source</td><td>The target and source branches are listed with an arrow pointing from the source to the target. Clicking a branch takes you to the branch's main page.</td></tr><tr><td>Reviewers</td><td>The Flosum Users who are assigned as reviewers of the Pull Request.</td></tr></tbody></table>

Clicking a Pull Request takes you to the request's overview page, where you can perform actions on it.

The **Three Vertical Dots** menu at the end of a Pull Request gives you the following options:

* **Edit**: Takes you to the edit Pull Request page to change: **Target branch**, **Source branch**, **Name**, and **Description**.
* **Close**: Terminates the Pull Request without merging. Once closed, the Pull Request is no longer shown in the Pull Requests list, and no more actions can be performed.

<figure><img src="https://1800549522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRpUu5iMlzMFAudyBvMOl%2Fuploads%2FXjfw7wQIo2BtQgHyFw0c%2FOverviewOfPullRequests-Overview-01.png?alt=media&amp;token=c9eae665-830c-4f34-bb5b-ddfc7e49078d" alt=""><figcaption></figcaption></figure>

### Searching, Sorting, and Filtering

The Pull Requests page can be searched, filtered, and sorted using the following tools.

* **Search** – search by Pull Request name or ID.
* **Authors** – filter by PR creator.
* **Status** – filter by state (Created, Review Requested, Changes Requested, Approved).
* **Reviewers** – filter by assigned reviewers.
* **Latest Activity** – sort Pull Requests by:
  * Sort by name A–Z – alphabetical order.
  * Sort by name Z–A – reverse alphabetical order.
  * Latest activity – most recent updates first.
  * Oldest activity – earliest updates first.
* **Date Range** – filter by creation or update timeframe. Use the date widget to enter a range.

### Pull Request Statuses <a href="#pull-request-statuses" id="pull-request-statuses"></a>

<table><thead><tr><th width="200">Status</th><th>Description</th></tr></thead><tbody><tr><td><strong>Created</strong></td><td>Pull Request opened but not reviewed.</td></tr><tr><td><strong>Review Requested</strong></td><td>Reviewers assigned but awaiting their feedback.</td></tr><tr><td><strong>Changes Requested</strong></td><td>Reviewers requested revisions before approval.</td></tr><tr><td><strong>Approved</strong></td><td>Pull Request is approved by reviewers and ready to merge.</td></tr></tbody></table>

## Pull Request Process

Pull Requests involve three key steps: creation, review, and merging. If conflicts arise during creation, they must be resolved prior to merging. Detailed guidance for each step is provided in the following articles.

* [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)
* [Resolving Pull Request Conflicts](/devops/pull-requests/pull-request-process/resolving-pull-request-conflicts.md)

{% hint style="success" %}

#### Best Practices

* Always review a Pull Request before merging feature or bug-fix branches.
* Write clear titles and descriptions for reviewers.
* Assign at least one reviewer for accountability.
* Resolve Pull Request conflicts before merging.
* Close stale Pull Requests to keep the list clean.
  {% endhint %}


---

# 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/overview-of-pull-requests.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.