git-branchless-prev(1)

💅 NAME 💅

Okay so this is the git-branchless-prev(1) page from the General Commands Manual, and the command is prev — move to an earlier commit in the current stack. That’s the vibe, bestie. 💖

🦋 SYNOPSIS 🦋

prev [-a|--all] [-b|--branch] [-o|--oldest] [-n|--newest]
[-i|--interactive] [-m|--merge] [-f|--force] [-h|--help] [NUM_COMMITS]

🌸 DESCRIPTION 🌸

Move to an earlier commit in the current stack. That’s it — that’s the whole main character moment, no cap. Literally just prev doing its little move-to-an-earlier-commit thing. ✨

🎀 OPTIONS 🎀

• -a, --all — traverse as many commits as possible. Go all the way, bestie. 💅
• -b, --branch — move the specified number of branches rather than commits. Branches, not commits — iykyk. 🌿
• -o, --oldest — when encountering multiple next commits, choose the oldest. Grandma commit rights 👑
• -n, --newest — when encountering multiple next commits, choose the newest. Fresh off the timeline ✨
• -i, --interactive — when encountering multiple next commits, interactively prompt which to advance to. Choose-your-own-adventure energy 🫶
• -m, --merge — if the local changes conflict with the destination commit, attempt to merge them. Make peace, not war 🤝
• -f, --force — if the local changes conflict with the destination commit, discard them. (Use with caution!) Like, for real, be careful 💀
• -h, --help — print help (see a summary with -h). The classic little help moment 🎀
• [NUM_COMMITS] — the number of commits to traverse. If not provided, defaults to 1. Lowkey important: default is one 👑

Manual source/version: git-branchless-prev(1) / prev; date: not shown on this page. Cute sign-off complete, bestie — catch you in the group chat 🫶💜🦋