Ferry: Jira-Driven Autonomous Development on GitHub Actions

Summary

Ferry is an innovative GitHub Actions-native agent pipeline designed to automate your development workflow. It seamlessly integrates with Jira, transforming column moves into reviewed draft pull requests without requiring any server or daemon. This tool empowers teams to achieve a fully autonomous development loop, from ticket refinement to merged PRs.

Use at your own risk

OSRepos shares public repositories for knowledge and discovery only. Any installation, execution, configuration, or use of code from these repositories is the user's own responsibility. Always review the repository, source code, dependencies, licenses, and security implications before running or installing anything. OSRepos is not responsible for issues, damages, or losses resulting from third-party repositories.

Introduction

Ferry is a powerful GitHub Actions-native agent pipeline that streamlines the development process by connecting your Jira board directly to an autonomous dev loop. It eliminates the need for manual intervention by converting Jira column transitions into reviewed draft pull requests, all without the overhead of a dedicated server or daemon. Built with TypeScript, Ferry offers a robust solution for automating your software delivery pipeline.

Why Use It and Benefits

Ferry provides significant advantages for teams looking to enhance their productivity and reduce manual effort. Its core benefit lies in creating a fully autonomous development workflow, where agents like Refiner, Developer, Reviewer, Iterator, and Merger run as GitHub Actions workflows. These are triggered automatically by Jira ticket column moves, ensuring a continuous and efficient flow from task assignment to code deployment. This automation minimizes human error, accelerates delivery times, and allows developers to focus on more complex tasks, while Ferry handles the repetitive aspects of the development cycle. It also supports experimental GitLab CI, expanding its utility.

Installation

Getting started with Ferry requires Node.js version 20 or higher and a Jira Cloud project. The installation process is straightforward, primarily involving a single command to initialize the setup.

npx -p @big-emotion/ferry ferry-init

After initialization, simply move a Jira ticket into your "Refinement" column, and Ferry will take over, orchestrating the subsequent development steps. For detailed instructions, including GitHub Actions and experimental GitLab CI paths, refer to the official installation guide.

Examples

Ferry's workflow is designed to be intuitive and highly automated. It follows a clear path:

Jira board  ??>  repository_dispatch  ??>  GitHub Actions  ??>  merged PR
   (you)              (automatic)           (autonomous)        (automatic)

This means that once a Jira ticket is moved, Ferry's agents automatically trigger a series of actions, leading to the creation and eventual merging of a pull request. Ferry also includes several CLI commands for managing your setup, such as ferry-init, ferry-doctor, ferry-update, and ferry-uninstall, providing comprehensive control over the automation pipeline.