watch-github-actions
Watch GitHub Actions
Monitor GitHub Actions workflow runs using the gh CLI.
Prerequisites
- The
ghCLI must be authenticated (gh auth status) - You must be in a git repository with a GitHub remote
Quick Status Check
List recent workflow runs for the current branch:
gh run list --branch "$(git branch --show-current)"
List all recent runs:
gh run list
Watch a Run in Real Time
Watch a workflow run until it completes:
gh run watch
Watch a specific run:
gh run watch <run-id>
This will continuously update the status until the run finishes (success, failure, or cancelled).
View Run Details
View a specific run with job details:
gh run view <run-id>
View with full log output:
gh run view <run-id> --log
View a failed job's log:
gh run view <run-id> --log-failed
Check Runs for a Specific Branch
Current branch:
gh run list --branch "$(git branch --show-current)"
Specific branch:
gh run list --branch main
gh run list --branch feature-branch
Check Runs for a PR
List workflow runs associated with a PR:
# Get the head branch of the PR, then list runs
BRANCH=$(gh pr view <pr-number> --json headRefName --jq '.headRefName')
gh run list --branch "$BRANCH"
Or view the checks directly on the PR:
gh pr checks <pr-number>
List Recent Runs
List runs for the current project:
gh run list
Filter by status:
gh run list --status failure
gh run list --status success
gh run list --status in_progress
Filter by workflow:
gh run list --workflow "CI"
JSON output for scripting:
gh run list --json databaseId,status,headBranch,url --jq '.[] | {id: .databaseId, status: .status, branch: .headBranch, url: .url}'
View Job Logs
View logs for a specific run:
gh run view <run-id> --log
View only failed job logs:
gh run view <run-id> --log-failed
Wait for Run Completion (Scripting)
Watch and wait for a run to complete:
RUN_ID=$(gh run list --branch "$(git branch --show-current)" --limit 1 --json databaseId --jq '.[0].databaseId')
gh run watch "$RUN_ID" --exit-status
echo "Run finished with exit code: $?"
Open Run in Browser
Open the latest run in your default browser:
gh run view --web
Open a specific run:
gh run view <run-id> --web
Rerun Failed Jobs
Rerun all failed jobs in a run:
gh run rerun <run-id> --failed
Rerun an entire run:
gh run rerun <run-id>
Useful Commands Reference
| Command | Description |
|---|---|
gh run list |
List recent workflow runs |
gh run list --branch <branch> |
List runs for a specific branch |
gh run list --status failure |
List failed runs |
gh run watch |
Watch latest run until completion |
gh run watch <run-id> |
Watch a specific run until completion |
gh run view <run-id> |
View run details and job list |
gh run view <run-id> --log |
View full run logs |
gh run view <run-id> --log-failed |
View only failed job logs |
gh run view --web |
Open run in browser |
gh run rerun <run-id> |
Rerun a workflow run |
gh run rerun <run-id> --failed |
Rerun only failed jobs |
gh run cancel <run-id> |
Cancel a running workflow |
gh pr checks <pr-number> |
View PR check statuses |
Common Flags
| Flag | Description |
|---|---|
-b, --branch |
Specify branch (default: current branch) |
--status |
Filter by status (queued, in_progress, etc.) |
--workflow |
Filter by workflow name |
-L, --limit |
Maximum number of runs to list |
-w, --web |
Open in browser |
--json |
Output as JSON with specified fields |
--jq |
Filter JSON output with jq expression |
Example Workflow
- Push your changes and create/update a PR
- Watch the workflow run:
gh run watch - If a job fails, view the failed logs:
gh run view <run-id> --log-failed - Rerun the failed jobs if needed:
gh run rerun <run-id> --failed
More from nvidia/openshell
openshell-cli
Guide agents through using the OpenShell CLI (openshell) for sandbox management, provider configuration, policy iteration, BYOC workflows, and inference routing. Covers basic through advanced multi-step workflows. Trigger keywords - openshell, sandbox create, sandbox connect, logs, provider create, policy set, policy get, image push, forward, port forward, BYOC, bring your own container, use openshell, run openshell, CLI usage, manage sandbox, manage provider, gateway start, gateway select.
11tui-development
Guide for developing the OpenShell TUI — a ratatui-based terminal UI for the OpenShell platform. Covers architecture, navigation, data fetching, theming, UX conventions, and development workflow. Trigger keywords - term, TUI, terminal UI, ratatui, openshell-tui, tui development, tui feature, tui bug.
4debug-inference
Debug why inference.local or external inference setup is failing. Use when the user cannot reach a local model server, has provider base URL issues, sees inference verification failures, hits protocol mismatches, or needs to diagnose inference on local vs remote gateways. Trigger keywords - debug inference, inference.local, local inference, ollama, vllm, sglang, trtllm, NIM, inference failing, model server unreachable, failed to verify inference endpoint, host.openshell.internal.
3debug-openshell-cluster
Debug why an OpenShell gateway deployment is unhealthy, unreachable, or unable to create sandboxes. Use when the user has a gateway health failure, Docker/Podman runtime issue, Helm install failure, Kubernetes scheduling issue, TLS secret issue, VM driver issue, or sandbox startup problem. Trigger keywords - debug gateway, gateway failing, deployment failing, helm install failing, cluster health, gateway health, gateway not starting, health check failed, sandbox pending, docker driver, podman driver, vm driver.
3triage-issue
Assess, classify, and route community-filed issues. Takes a specific issue number or processes all open issues with the state:triage-needed label in batch. Validates agent-first gate compliance, attempts diagnosis using relevant skills, and classifies issues for routing into the spike-build pipeline. Trigger keywords - triage issue, triage, assess issue, review incoming issue, triage issues.
2create-spike
Investigate a plain-language problem description by deeply exploring the codebase, then create a structured GitHub issue with technical findings. Prequel to build-from-issue — maps vague ideas to concrete, buildable issues. Trigger keywords - spike, investigate, explore, research issue, technical investigation, create spike, new spike, feasibility, codebase exploration.
2