Skip to content

Fix typo on Branch Review page #6272

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 12, 2025
Merged

Fix typo on Branch Review page #6272

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/cloud/features/branch-review.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ Compare which tests are failing, flaky, pending, added, or modified between the
UI Coverage or Cypress Accessibility changes between runs will also appear here.

Branch Review is useful even if you do not have a Pull Request workflow, because it allows you to compare any two runs of your choice.
These might might represent different builds of the application, changes in test code, or results from nightly runs. This page will use
These might represent different builds of the application, changes in test code, or results from nightly runs. This page will use
the example of a Pull Request made using the GitHub integration, but this integration is not required in order to use Branch Review.

A common scenario throughout the software development lifecycle (SDLC) is an engineer's **feature** branch that will be merged into the
Expand Down