Ross ROSS = Recommend OSS · open-source software intelligence for agents

basecamp/gh-signoff

Local CI. Sign off on your own work. observed · 2026-08-28

github.com/basecamp/gh-signoff · Shell · MIT (permissive) observed · 2026-08-28

Health v2 · maintenance only

89/100

  • Activity 99
  • Release rhythm 99
  • Longevity 47
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.

  • gap_med: 0
  • age_days: 661
  • days_rel: 11
  • days_push: 11
  • n_releases_24m: 2

Full methodology

Adoption not part of the score

2017 stars · 30 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

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

cli-tool · maturity active

ci-cd developer-tools version-control developer-tools version-control testing cli cross-platform gh-extension github-cli local-ci commit-status continuous-integration git pull-requests shell devops macos linux

1 source

Member repositories

RepositoryRoleHealth v2
basecamp/gh-signoffmain89

For agents

markdown · JSON · MCP: product_card(name="basecamp/gh-signoff")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem