git-branchless-reword(1)

🎀 NAME 🎀

okay so bestie, welcome to git-branchless-reword(1) from the General Commands Manual — the main character is reword, and its whole thing is rewording commits. no cap, that's the name-section moment ✨

💅 SYNOPSIS 💅

reword [--hidden] [-f|--force-rewrite] [-m|--message] [--fixup]
[-d|--discard] [-h|--help] [REVSETS]

🌸 DESCRIPTION 🌸

reword rewords commits. that's it, that's the description, and honestly it's giving exactly what it says on the tin 🫶

✨ OPTIONS ✨

• --hidden — include hidden commits in the results of evaluating revset expressions. lowkey essential when the commit you want is being shy 🙈
• -f, --force-rewrite — force rewording public commits, even though other people may have access to those commits. bestie, this is the shared-history danger zone, so read that twice before you slay 💀
• -m, --message <MESSAGES> — the commit message to use. multiple messages will be combined as separate paragraphs, similar to git commit. if not provided, you will be prompted to provide a commit message interactively. put those paragraphs in and let it cook 🍓
• --fixup <COMMIT_TO_FIXUP> — a commit to "fix up". the message will be prefixed with fixup! following the supplied commit, suitable for use with git rebase --autosquash. this is the autosquash-friendly one, iykyk 🔥
• -d, --discard — throw away the original commit messages. if commit.template is set, then the editor is pre-populated with that; otherwise, the editor starts empty. clean-slate energy, but literally 🧚
• -h, --help — print help (see a summary with -h). yes bestie, the help option is helping you get help 😭
• [REVSETS] [default: stack() | @] — zero or more commits to reword. default is stack() | @, because of course it is 🌈

---

that's the tea, bestie 💖 source/manual: git-branchless-reword(1); version/date: not listed in the footer, so this is the cute sign-off instead 🎀✨