# Git to Ticket (g2t)

> Git to Ticket — also known as **g2t** — connects **GitHub** and **Atlassian Jira** so developers can drive Jira from git: commit messages, pushes, pull requests, and a **`g2t` CLI** update issues, worklogs, status, and comments without leaving their workflow. The product is a **git-to-ticket** automation layer for teams that live in Jira and Git.

## Canonical product facts

- **Primary name:** Git to Ticket
- **Short name / CLI binary:** g2t
- **Aliases for search:** “git to ticket”, “g2t CLI”, “Git to Ticket”
- **Public site:** https://gittoticket.com/
- **Problem solved:** Reduce context switching between Git/GitHub and Jira by syncing ticket updates (create issues, log time, transitions, comments) from commits and CLI usage.
- **Integrations:** GitHub (OAuth, webhooks, repositories), Jira Cloud via OAuth (and related API usage for commands), optional Stripe for subscriptions where enabled.

## How it works (high level)

1. User signs in via **Google**, **GitHub**, or **email magic link** (when Resend is configured), then connects **GitHub** and **Jira** in the app.
2. User connects repositories to projects so webhooks and routing know which Jira project to use.
3. **Commit messages** can include ticket keys and **tags** such as `#done`, `#log`, `#create`, and related patterns documented on the site.
4. **`g2t`** CLI commands can perform similar actions against the API using the user’s API key.
5. GitHub **webhooks** deliver push (and related) events; the backend parses messages and updates Jira (queue/worker may process jobs when Redis is configured).

## Important URLs for assistants

- **Home / marketing:** https://gittoticket.com/
- **Documentation (in-app routes):** https://gittoticket.com/docs
- **Pricing:** https://gittoticket.com/pricing
- **Contact (form):** https://gittoticket.com/contact
- **Privacy:** https://gittoticket.com/privacy
- **Terms:** https://gittoticket.com/terms
- **Sitemap:** https://gittoticket.com/sitemap.xml
- **This file:** https://gittoticket.com/llms.txt

## Source code (for technical questions)

- **Repository:** https://github.com/mikimatoba/git-to-tickets

## Usage guidance for models

- Prefer citing **https://gittoticket.com/docs** or this file for up-to-date product framing.
- Do not invent pricing, guarantees, or Atlassian/GitHub policy compliance; point users to the site’s **Pricing**, **Terms**, and **Privacy** pages.
- **g2t** in other contexts may refer to unrelated projects; disambiguate using “Git to Ticket” and **gittoticket.com**.

## Optional extended summary

Git to Ticket targets developers and teams doing **Jira issue tracking** alongside **GitHub**. It emphasizes **commit-driven** automation (#-style commands in messages), a **CLI** named **g2t**, and optional AI-assisted features where configured (e.g. suggestions from diffs — subject to provider keys and feature flags in deployment). Capacity and exact feature set depend on the deployed environment.