hub-ci-status

Check the CI status for this branch

$ hub ci-status [[-v|--verbose]]

$ hub ci-status [[-v|--verbose]] [commit_SHA]

hub ci-status [-v] [-o PROVIDER] [REF]

-v, --verbose
    Show detailed status with URLs and descriptions

-o, --provider PROVIDER
    Filter by CI provider (e.g., github, travis, circleci, github-actions, gitlab, jenkins)

REF
    Git ref/SHA (branch/tag/commit); defaults to current branch

hub ci-status queries the GitHub API to show the status of Continuous Integration (CI) checks for a specified ref (branch, tag, or commit SHA), defaulting to the current branch. It aggregates statuses from various CI providers, indicating if checks are passing (✓), failing (✗), pending, or unknown.

Supported providers include GitHub Actions, Travis CI, CircleCI, Jenkins, GitLab CI, AppVeyor, and many others. The command helps developers quickly assess if a branch is ready for merge by reviewing CI results without opening the GitHub UI.

Output is color-coded: green for success, red for failure, yellow for pending. Verbose mode (-v) provides detailed URLs and descriptions for each check. It requires hub to be authenticated via GitHub token or SSH.

This tool enhances Git workflows by integrating CI visibility directly in the terminal, ideal for CI/CD pipelines and pre-merge checks.

Requires GitHub authentication; limited to GitHub-hosted repos; deprecated in favor of gh CLI; may not show all custom CI setups.

hub ci-status # Current branch status
hub ci-status -v origin/pr/123 # Verbose PR status
hub ci-status -o travis HEAD~1 # Travis only, previous commit

Full list: github, travis, travis-org, travis-pro, circleci, drone, semaphore, codeship, buildkite, concourse, bucketeer, taskcluster, gitlab, appveyor, shippable, jenkins, bitrise, teamcity, bamboo, gocd, buildhub, azure, bitbucket, github-actions

Introduced in hub 2.2.0 (2016) by GitHub Inc. Actively developed until 2021; now maintenance-only as gh CLI supersedes it.

hub(1), git(1), gh ci view(1)