Follow GitHub Actions after a merge

Keep an eye on your pull request's workflows without pausing your next task. Choro links GitHub Actions progress to the Ship in your conversation and shows a separate status in the companion.

Start tracking

Merge your pull request with Choro's Ship flow. Choro checks for workflows associated with the merge. Once runs are found, a GitHub Actions card appears beneath its Ship. For an earlier Ship that is not being tracked, use Check Actions.

Your repository needs GitHub Actions workflows that run for the merge. If no matching runs are found, Choro shows that status rather than inventing a result.

Read the status

The card identifies the repository, pull request, base branch, and merge commit, with the workflows Choro found. Follow queued or running workflows and their results, or see when approval is needed on GitHub. Open on GitHub takes you to GitHub to inspect the details or handle an approval.

Workflow status and agent activity are separate, so you can keep chatting, start another task, or ship another change while workflows run.

Refresh, stop, or resume

Use Refresh to check again. Choose Stop tracking from the card's menu when you no longer want Choro to monitor it. This stops Choro's monitoring; it does not cancel workflows on GitHub. Use Resume when you want to start monitoring again. Tracking state is saved across Choro restarts.

Investigate a failure

When a failed workflow offers Ask agent to investigate, click it to prepare a request with the relevant run links. Choro keeps existing composer text and does not send automatically. Review the request, then send it when you are ready.

If results have not appeared

If Choro is still checking, allow time for GitHub to create the runs, then refresh. If no runs are found, check on GitHub that a workflow runs for that branch or merge. If GitHub cannot be reached, Choro shows a connection message and retries; the last known status is not proof of a fresh check.

A successful GitHub Actions result confirms the reported workflows succeeded. It does not by itself confirm that your app is deployed or live.