> For the complete documentation index, see [llms.txt](https://docs.bluestorm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluestorm.io/dashboards/policies/compare-revisions.md).

# Compare Revisions

The compare revisions page enables you to compare the policy results of 2 different revisions for the same app. This makes it possible to view changes between 2 versions of the same app. This page is accessed by first selecting a revision to compare from the 'Revisions' tab in the [app page](https://docs.bluestorm.io/dashboards/app.md), and then clicking the 'compare' link.

The branch and revision of the first revision are automatically selected. Select the branch and revision to compare to. Note, only revisions that have already been checked are visible in the selector. Also, it makes sense to select an older revision for revision 2 so that you can see what improvements you have made in revision 1.

After clicking 'compare' the results page will appear:

<details>

<summary>Comparison Results</summary>

The comparison results card shows a summary of what has changed in revision 1 compared to revision 2:

* **New.** New check results that did not exist in revision 2.
* **Unchanged.** Check results that are in both revision 1 and revision 2.
* **Resolved.** Check results that are in revision 2, but that are no longer in revision 1.

</details>

<details>

<summary>Check Results (Revision 1)</summary>

The check results overview will show the policy results for revision 1. In addition to the standard check result details an extra colum 'Status' shows if the check result is new, unchanged, or resolved in comparison to revision 2.

</details>


---

# 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.bluestorm.io/dashboards/policies/compare-revisions.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.
