git town commit
git town commit [-d | --down uint] [--dry-run] [-h | --help] [(-m | --message) <text>] [-v | --verbose]The commit command takes the currently staged changes and commits them into a different branch in your stack, then synchronizes the result back into your current branch.
This is useful when working with stacked branches. A common scenario is that you’re implementing a feature and realize that part of the work is an independent change, let’s say a refactor, and that part belongs in a different branch because you want it reviewed and shipped independently. Since the feature depends on it, the refactor must live in an ancestor branch.
Your desired branch stack looks like this:
main
\
refactor
\
feature
Manually switching back and forth between refactor and feature to commit
into the correct branch and move changes around is slow and error-prone.
When using git town commit, you can stay on the feature branch, do the
refactoring there to make sure everything works, and then commit the refactoring
changes directly into the refactor branch. Git Town will automatically sync
the committed changes back into feature, letting you continue where you left
off.
Options
-d uint
--down uint
Commit the staged changes into the ancestor branch that is the given number of generations older than the current branch.
--downand--down=1commit into the parent branch--down=2commits into the grandparent branch--down=3commits into the great-grandparent branch
--dry-run
Print the Git commands that would be executed without actually running them.
-h
--help
Display help for this command.
-m <text>
--message <text>
Set the commit message from the command line, equivalent to git commit -m.
-v
--verbose
Prints all Git commands executed under the hood, used to determine repository state.