# Overview of Pull Requests

## ![](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.

## 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 these 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 that created the Pull Request.</td></tr><tr><td>Lastest Activity</td><td>The amount of time since the lastest activity for the Pull Request.</td></tr><tr><td>Tartet 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 branches main page.</td></tr><tr><td>Reviewers</td><td>The Flosum Users that are assigened 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&#x26;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 reviesions before approval.</td></tr><tr><td><strong>Approved</strong> </td><td>Pull Request is approved by reivewers 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](https://docs.flosum.com/devops/pull-requests/pull-request-process/pull-request-step-1-creating "mention")
* [pull-request-step-2-reviewing](https://docs.flosum.com/devops/pull-requests/pull-request-process/pull-request-step-2-reviewing "mention")
* [pull-request-step-3-merging](https://docs.flosum.com/devops/pull-requests/pull-request-process/pull-request-step-3-merging "mention")
* [resolving-pull-request-conflicts](https://docs.flosum.com/devops/pull-requests/pull-request-process/resolving-pull-request-conflicts "mention")

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