Track pull requests and workflow checks
Find pull requests and inspect the progress of Choro Git Workflows.
Last updated 16 September 2026
Find pull requests and inspect the progress of Choro Git Workflows.
Before you start
Use the intended repository with a supported remote and account access. Git Workflows require a secure GitHub origin and its connected GitHub CLI account.
Use Git’s view menu to move from local changes and commits to pull requests and Choro Git Workflows.
Step by step
Open Git and use the view menu to choose Pull requests. Confirm the repository when your project contains more than one.
Read the PR’s status, number, and source-to-base branch direction. Open its row to inspect the PR on the hosting service.
Review the latest checks, requested changes, and merge requirements on that PR. A successful older run does not establish the status of a newer commit.
Choose Workflows to inspect Choro’s saved branch-promotion workflows and their current or recent runs.
Read the workflow route and completion policy. Confirm before merge waits for a decision; Auto-merge when ready has different effects and still depends on GitHub protections.
For a blocked or failed run, read the reported reason and inspect the associated PR before retrying or reviewing a merge.
If the view cannot load, check repository selection, remote configuration, and account access. An authentication or missing-remote error does not mean there are no pull requests.
What to expect
You can connect a local change to its PR and distinguish review, checks, and workflow completion.
Troubleshooting and useful details
The screenshot identifies the Git views. Choro Git Workflows promote committed work between remote branches through pull requests; they are not the same thing as an individual GitHub Actions job. Starting or merging a workflow changes remote state, so inspect its route and policy first.