fotingo

Fotingo

A CLI to streamline workflows across Git, GitHub, and Jira.

Overview

Fotingo helps you:

• Start working on Jira issues with consistent branch naming
• Create pull requests with issue context and metadata
• Manage stacked pull request chains, including worktree-aware rebases
• Open related URLs for branch, issue, PR, and repository
• Inspect local branch/issue context as JSON
• Automate command flows with machine-readable output

Installation

From source

go install github.com/tagoro9/fotingo@latest

From binary

Download the latest release from the releases page.

Homebrew

brew tap tagoro9/tap
brew install fotingo
xattr -dr com.apple.quarantine /opt/homebrew/bin/fotingo

On macOS, Homebrew can preserve the com.apple.quarantine attribute on downloaded binaries. Because fotingo is a standalone CLI binary distributed outside the App Store, Gatekeeper may block execution until that quarantine attribute is removed. Running xattr -dr com.apple.quarantine /opt/homebrew/bin/fotingo clears the attribute so the binary can run normally.

Quick Start

Prerequisites:

1. GitHub authentication:
   • Fotingo GitHub App installed in the orgs you want to access (it can be installed during the auth flow), or
   • A classic GitHub PAT from https://github.com/settings/tokens with repo scope
2. Jira authentication:
   • Atlassian API token from https://id.atlassian.com/manage-profile/security/api-tokens, or
   • Atlassian Cloud service-account scoped token with Jira root https://api.atlassian.com/ex/jira/{cloudId}, or
   • OAuth only in internal binaries compiled with Jira OAuth client credentials
3. Jira account email
4. Jira server URL (for example https://yourcompany.atlassian.net) or Atlassian Cloud API root

Jira OAuth client credentials include a client secret and are intended for internal builds only. Committing or broadly distributing binaries with embedded Jira OAuth client secret is not considered safe.

Basic flow:

# Authenticate services
fotingo login

# Start work on an issue
fotingo start PROJ-123

# Create a pull request for current branch
fotingo review -y

# Create a child PR stacked on an open parent PR branch
fotingo review -y --branch feature/PROJ-122-parent

# Inspect and refresh the current stacked PR chain
fotingo review stacks
fotingo review stacks sync

# Inspect pull request comments and review conversations
fotingo inspect pr --json

# Refresh selected PR sections or metadata after follow-up changes
fotingo review sync --section changes --section fixed-issues -y

# Open the PR in browser
fotingo open pr

fotingo start auto-stashes only tracked or staged changes. Untracked-only files and directories stay in place. When branch creation needs a base refresh, fotingo checks only the default branch and does not use shallow fetches during that preflight step.

For full authentication setup details, see docs/authentication.md.

Common Commands

For flags, JSON contracts, and examples, see the CLI Reference and Automation and JSON docs.

Telemetry

Fotingo emits anonymous product telemetry to understand command usage, latency, and failures.

• Enabled by default (telemetry.enabled: true)
• Opt out anytime:

fotingo config set telemetry.enabled false

• Telemetry never sends raw tokens, freeform descriptions/titles, branch names, issue IDs, or raw API URLs.

See docs/telemetry.md for event categories and privacy constraints.

Documentation

User and maintainer docs live in docs/:

• Breaking Changes v5
• Authentication
• CLI Reference
• Configuration
• Telemetry
• Automation and JSON
• Shell Completion
• Exit Codes
• Release Operations
• Homebrew Tap Setup

Why Fotingo?

Jira-backed development often repeats the same sequence:

1. Pick/assign an issue
2. Move it to In Progress
3. Create a correctly named branch
4. Implement and commit
5. Open and enrich a PR
6. Move issue to In Review and add PR link

Fotingo turns this into a small set of consistent commands.

What is a Fotingo?

In Canary Islands Spanish, "fotingo" means an old, rickety car. One origin story links it to Ford's "foot 'n go" phrase from the Model T era. The name fits the CLI goal: minimal friction to get moving.

Contributing

Contributions are welcome. Open an issue or submit a pull request.

License

MIT License. See LICENSE.