# basecamp/gh-signoff

Local CI. Sign off on your own work.

Repository: https://github.com/basecamp/gh-signoff
Canonical: https://ross.abutalabs.com/products/gh-signoff
Language: Shell
License: MIT
License Family: permissive
Topics: gh-extension
Last push: 2026-08-22T08:16:55+00:00

## Health v2 (maintenance only)
Score: 89/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 99, release rhythm 99, longevity 47
- inputs: {"age_days": 661, "days_push": 11, "days_rel": 11, "gap_med": 0, "n_releases_24m": 2}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 2017, forks 30 (observed 2026-08-28T04:06:05.545653+00:00)

## What it is
A GitHub CLI extension (written in Shell) that brings CI in-house: you run your test suite on your own machine and then run `gh signoff` to post a green commit status on your pull request. It targets the trade-off where cloud CI runners are slow, expensive, and overkill for apps that just need a passing status check.

## Use cases
- run CI locally without paying for cloud CI runners
- set a green commit status on a GitHub PR without a CI server
- sign off on a pull request after my tests pass locally
- replace GitHub Actions for a small side project
- mark commits as verified from my own machine
- point a PR status check's Details link at a local run or dashboard

## When to choose
- You work on a small app or solo project where high-ceremony CI is overkill
- You want a green GitHub commit status without renting cloud CI
- Your team already has solid test/push/deploy discipline and fast dev machines
- You want checks to run on your own underutilized hardware for speed and zero cost

## When to avoid
- You need repeatable builds, parallelized execution, or comprehensive cross-environment test matrices
- You require enforced, tamper-proof verification on a shared remote runner rather than trusting developers
- Your workflow depends on merge queues, deployment pipelines, or CI gating merges
- You can't rely on team members actually running the test suite before signing off

## Facets
- artifact type: cli-tool
- maturity: active
- function: ci-cd, developer-tools, version-control
- domain: developer-tools, version-control, testing
- platform: cli, cross-platform
- tags: gh-extension, github-cli, local-ci, commit-status, continuous-integration, git, pull-requests, shell, devops, macos, linux

## Member repositories
- basecamp/gh-signoff (main) score 89

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:06:05.545653+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T03:00:38.428665+00:00, confidence not recorded.
  - readme: https://github.com/basecamp/gh-signoff (fetched 2026-08-28T04:06:05.545653+00:00, sha 14a4bf52de3e)
- Data as of 2026-08-30T08:39:29.467469+00:00.