git-branchless-next(1)

okay so welcome to git-branchless-next(1), bestie — this is the next command, straight outta the General Commands Manual 💖

🎀 NAME 🎀

next — move to a later commit in the current stack ✨

🦋 SYNOPSIS 🦋

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

🌸 DESCRIPTION 🌸

Move to a later commit in the current stack. That's the whole vibe — later commit, current stack, main character energy 🫶

💅 OPTIONS 💅

• -a, --all — traverse as many commits as possible 👑 go off, bestie.
• -b, --branch — move the specified number of branches rather than commits. yes, branches, not commits — iconique 🎀
• -o, --oldest — when encountering multiple next commits, choose the oldest 🕰️
• -n, --newest — when encountering multiple next commits, choose the newest ✨
• -i, --interactive — when encountering multiple next commits, interactively prompt which to advance to 👀 iykyk.
• -m, --merge — if the local changes conflict with the destination commit, attempt to merge them 🤝 teamwork.
• -f, --force — if the local changes conflict with the destination commit, discard them. (Use with caution!) 💀

not me warning you for real: this one discards local changes. Use with caution! periodt.

• -h, --help — print help (see a summary with -h) 🫶
• [NUM_COMMITS] — the number of commits to traverse. If not provided, defaults to 1. literally one by default, no cap 🌸

okay that's the whole page, bestie — footer vibes were just next and git-branchless-next(1), with no extra source/version/date line to report, so I'm not inventing one 🫶💜