← Back to home
Comparison · Infra & APIs

gh vs rush

A side-by-side editorial comparison of gh and rush — release velocity, themes, recent moves, and the top alternatives to consider.

gh vs rush: at a glance

Featureghrush
SectorInfra & APIsInfra & APIs
Velocity score2.52.5
Sparks · 30d00
Top themesgithub-api, http-client, pagination, token-handlingmlr3, distributed-computing, redis, fault-tolerance
Last editorial update2h ago3h ago
WebsiteVisit →Visit →

What is gh?

gh spent its last two releases making failures and interruptions recoverable.

The GitHub API client rebuilt on httr2 in 1.4.0, then took a security-driven breaking change in 1.5.0: response headers are no longer stored in returned objects, because they can carry sensitive information. The 1.6.0 release made interrupted pagination recoverable and downgraded personal access token format validation from an error to a warning.

Read the full gh trajectory →

What is rush?

Rush spent 2026 making distributed task ownership correct, starting with a breaking 1.0.

rush is the Redis-backed distributed computing backend behind mlr3's parallel tuning: workers pull tasks, push results and are tracked through heartbeats. Since 1.0.0 in March 2026 it has shipped five releases in four months, almost all correcting how tasks and workers are owned and identified under failure. The most recent lets each worker start in its own mirai call so it can spawn local daemons.

Read the full rush trajectory →

gh vs rush: editorial side-by-side

G
gh
INFRA · APIS
2.5

gh spent its last two releases making failures and interruptions recoverable.

◆ Current state

The GitHub API client rebuilt on httr2 in 1.4.0, then took a security-driven breaking change in 1.5.0: response headers are no longer stored in returned objects, because they can carry sensitive information. The 1.6.0 release made interrupted pagination recoverable and downgraded personal access token format validation from an error to a warning.

◆ Where it's heading

The direction is tolerance for partial and unusual outcomes rather than new endpoint coverage. Interrupting a paginated call now raises a classed condition carrying the records already fetched; a 304 Not Modified returns an empty response with headers intact instead of erroring; an unrecognised token format warns and proceeds. A fake_github_app() built on webfakes ships for testing, and is offered to other package authors.

◆ Prediction

Token format handling is now configurable rather than fixed, so the next likely work is following GitHub's credential formats as they change, not expanding the client surface.

R
rush
INFRA · APIS
2.5

Rush spent 2026 making distributed task ownership correct, starting with a breaking 1.0.

◆ Current state

rush is the Redis-backed distributed computing backend behind mlr3's parallel tuning: workers pull tasks, push results and are tracked through heartbeats. Since 1.0.0 in March 2026 it has shipped five releases in four months, almost all correcting how tasks and workers are owned and identified under failure. The most recent lets each worker start in its own mirai call so it can spawn local daemons.

◆ Where it's heading

The through-line is moving responsibility from the controller to the worker. 1.0.0 rewrote the task lifecycle and dropped the seed mechanism; 1.2.0 moved fail_tasks(), finish_tasks(), pop_task() and push_running_tasks() from Rush onto RushWorker so only the worker that ran a task can mark it done, and gave worker ids random suffixes so they cannot collide. 1.1.0 had already removed phantom failed tasks when a worker crashes between evaluations.

◆ Prediction

With ownership and identity settled, the remaining pressure points are heartbeat and lost-worker detection; expect the next releases to tighten failure recovery rather than add API surface.

Alternatives to gh and rush

Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either gh or rush.

See all gh alternatives → · See all rush alternatives →

Recent activity from gh and rush

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 21d agorushWorkers start in their own mirai call so they can create local daemons
  2. 25d agoghPagination progress bar reports true record counts
  3. 1mo agorushTask lifecycle moves onto the worker; worker ids can no longer collide
  4. 2mo agoghInterrupted pagination keeps its partial results
  5. 3mo agorushPhantom failed tasks and missed results fixed
  6. 4mo agorushSmaller Redis payloads and vector-valued task parameters
  7. 4mo agorushRush 1.0 rewrites the task lifecycle and drops the seed mechanism
  8. 9mo agorushwait_for_workers() can target a count or specific ids
  9. 1y agoghResponse headers dropped from results after a security advisory
  10. 2y agoghPagination helpers repaired and atomic file writes
  11. 3y agoghClient rebuilt on httr2 with rate-limit controls
  12. 3y agoghLower-case methods and richer error conditions

Frequently asked questions

What is the difference between gh and rush?

They serve adjacent needs but don't currently overlap on shipped themes. gh and rush are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is gh better than rush?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. gh and rush are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to gh?

Top gh alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "gh alternatives" section above for the current picks, or visit /alternatives/gh for the full list with editorial commentary on each.

What are the best alternatives to rush?

Top rush alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "rush alternatives" section above for the current picks, or visit /alternatives/rush for the full list with editorial commentary on each.