With the CLI installed, you can now learn more about the recommended workflow and terminology for the core commands..
gt create
to create branches, gt submit
to turn those branches into pull requests, gt modify
to make changes to your branches, and gt sync
to synchronize with your GitHub remote repository.
gt
commands.gt --help
or command-specific help with gt <command> --help
gt
will pass any unrecognized commands through to git
. For example, you can run commands like gt add
or gt status
successfully even though they aren’t native commands in gt
—and you’ll see a message like this:
git
passthrough helps to avoid confusion about when to use gt
vs. git
. You should be able to use gt
for everything in your git
workflow!
git
branches that depend on each other. It starts at main
(or whatever your trunk branch may be called), and proceeds “upward” as dependent branches are stacked on. Commands with the stack
parent command operate on all ancestors and descendants of a branch.
main
). There are many Graphite commands that accept --trunk
flags to operate on or in reference to the trunk branch of the repository.
main
in a stack (more recent; descendants; recursive children).
main
in a stack (less recent; ancestors; recursive parents).
gt
commands have an “alias,” or shortened form. Graphite also allows you to configure your own aliases for commands, to fit your workflow best.