Jitly vs GitHub CLI: which one actually saves you time

gh is great for PRs and issues, but it doesn't know anything about Jira. Here's where the two overlap and where they don't.

I use gh a lot, honestly it's one of my favorite CLIs. Creating PRs from the terminal, checking CI status, reviewing diffs — it's all quick and it works well. So people sometimes ask me why I'd bother with Jitly if gh already exists.

The thing is, gh doesn't touch Jira at all. It doesn't know your ticket is ABC-123, it doesn't know your team's branch naming rule, and it definitely isn't moving your Jira card to Done when you push. Those are two completely different problems.

Where they overlap

Not much really. gh is built around GitHub's PR/issue model. Jitly is built around the "I have a Jira ticket, now what" workflow. If your team uses GitHub Issues instead of Jira, honestly gh probably covers you fine and you don't need Jitly at all.

Where Jitly wins

Automatic branch naming based on the ticket, no more guessing what convention the team uses this month
Jira status changes without opening a browser tab
Standup generation from your actual commits

Verdict: if your team lives in Jira, use both — gh for the PR side, Jitly for the ticket-to-branch side. They don't compete, they just cover different halves of the day.

← Back to blog