Git commands every developer should actually know (and what Jitly runs for you)

A practical list of git commands, grouped by when you'd use them, plus what Jitly automates from this list.

There are hundreds of git commands and flags. Here's the shortlist that covers almost everything you'll do in a normal week, organized by when you'd reach for each one.

Starting work

git checkout main
git pull origin main
git checkout -b feature/abc-123-fix-login

This is exactly what jitly start ABC-123 runs for you, except the branch name is built from your policy template instead of typed by hand.

While working

git status
git diff
git add .
git commit -m "ABC-123: fix login redirect loop"

Jitly doesn't touch this part — the actual coding and committing along the way is still on you, as it should be.

Wrapping up

git add .
git commit -m "final message"
git push --set-upstream origin feature/abc-123-fix-login

jitly done runs this sequence and also pushes the Jira ticket to whatever status you pick, fetched live from your Jira workflow so it always matches what your team actually has configured.

Checking on things

git log --oneline -10
git branch -a
git status

jitly status gives you a similar summary — active ticket, active branch, and git state — without needing three separate commands.

When something's stuck

git stash
git stash pop
git checkout -- .

This is the exact set of options Jitly offers you when you try to jitly start a new ticket while you've got uncommitted changes sitting around — stash it, push it, or discard it, instead of you having to remember the right git incantation under pressure.

← Back to blog