ferry vs no-mistakes
Jira-triggered coding workflows compared with Git push validation
ferry turns Jira column changes into agent-driven development workflows, primarily through GitHub Actions, and can prepare draft pull requests. no-mistakes gates Git pushes through a local validation pipeline in a disposable worktree, then forwards passing changes and opens a pull request.

ferry: Automate Jira-to-PR Workflows with GitHub Actions
Ferry is a Jira-driven agent pipeline built on GitHub Actions, with experimental GitLab CI support. Jira column moves trigger agents that refine tickets, develop and review code, then prepare draft pull requests for your team.

no-mistakes: Gate Git Pushes with AI Validation
no-mistakes is a Go-based local Git proxy for macOS, Linux, and Windows. It runs an AI-driven validation pipeline in a disposable worktree, then forwards passing changes and opens a pull request.
| ferry | no-mistakes | |
|---|---|---|
| Language | TypeScript | Go |
| License | MIT | MIT |
| Stars | 4 | 9k |
| Forks | 1 | 930 |
| Last analyzed | Oct 25, 2026 | Oct 26, 2026 |
Key differences
- ferry starts work from configured Jira column transitions; no-mistakes starts when a developer pushes to its Git proxy.
- ferry covers refinement, development, review, and merging; no-mistakes focuses on validating, cleaning up, and forwarding changes through configurable steps.
- ferry is written in TypeScript and runs primarily on GitHub Actions, with experimental GitLab CI support; no-mistakes is written in Go and runs as a local Git proxy on macOS, Linux, and Windows.
- ferry connects Jira tickets to repository work and can use a local runner with per-ticket worktrees; no-mistakes isolates pipeline checks in a disposable worktree and offers Git push, terminal UI, and agent-skill entry points.
- ferry is marked quiet, with no commits in the last 90 days; no-mistakes is described as actively maintained, with issues and pull requests handled quickly.
- Both use the MIT license; the supplied facts list 4 stars and 1 fork for ferry, and 9k stars and 930 forks for no-mistakes.
Choose ferry if you…
- need Jira column transitions to trigger agent-assisted implementation and review.
- want a GitHub Actions workflow that can prepare draft pull requests from Jira tickets.
- prefer an operator-managed local runner with per-ticket worktrees or want to evaluate the experimental GitLab CI path.
Choose no-mistakes if you…
- want a local gate between your branch and its push target, with checks isolated from your working tree.
- need support for multiple coding-agent CLIs and automatic safe mechanical fixes, with judgement calls left to a person.
- want passing changes forwarded and a pull request opened, with an optional guarded flow for CI failures.
Compare the numbers side by side, or add more projects
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.