> For the complete documentation index, see [llms.txt](https://docs.flxbl.io/flxbl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flxbl.io/flxbl/codev/development/validation-and-pull-requests.md).

# Validation reports and pull requests

The **Review** group under Dev holds the two surfaces that support code review: the reports produced when you validate a commit, and an overview of the project's pull requests.

## Validation reports

Every commit you [validate from Source Control](/flxbl/codev/development/development-workflow.md#validate-a-commit) stores its report, and **Dev > Review > Validation Reports** lists them — one card per validated commit on your current branch, with the outcome, the packages that were validated, and when the validation ran. Search by message, hash, or author, or filter by status.

<figure><img src="/files/jjBTwoNGbaEqc5Zz33Cj" alt="The Validation Reports page with a report card showing a successful validation of a commit and its validated package"><figcaption><p>Validation Reports — one card per validated commit on your branch.</p></figcaption></figure>

**View Report** opens the full report: the outcome, the deployment result per package, the Apex tests that ran, and coverage against the threshold. **Copy Markdown** copies the report for sharing — into a pull request description, for example.

<figure><img src="/files/h1UMa2hcFHqMpBkxfH9s" alt="A validation report dialog showing the summary, validated packages, deployment result, and Apex tests"><figcaption><p>The validation report — deployment, tests, and coverage for the commit.</p></figcaption></figure>

Reports follow your branch: the list covers the commits your current branch is ahead of its target, so once a commit merges, its report leaves the list.

## Pull requests

**Dev > Review > Pull Requests** is the project-wide view of pull requests — every author, not just yours. Each row shows the pull request with its state and source branch, the provider's check status, and how the branch stands against its target: commits ahead, commits behind, or **In Sync**, with the pull request's age.

<figure><img src="/files/AW2n3cenrasJZudVrRtE" alt="The Pull Requests page listing the project&#x27;s open pull requests with check status and ahead/behind sync information"><figcaption><p>Pull Requests — the project's pull requests with check status and branch sync state.</p></figcaption></figure>

Filter by **State** (open, merged, closed) or **Author**, or search by number, title, branch, or author. **Open** takes you to the pull request at your source-control provider.

The list is served from the codev server, which refreshes its snapshot of the provider periodically; **Refresh** requests a fresh one.

{% hint style="info" %}
This page is the read-only overview. Acting on your own branch — validating commits, creating a pull request — happens on [Source Control](/flxbl/codev/development/development-workflow.md#commit-your-work-source-control), whose Commits & PRs tab shows your branch's pull requests alongside its commits.
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.flxbl.io/flxbl/codev/development/validation-and-pull-requests.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.