workflow branch
Start work on an issue: create its branch, named by the convention, and switch to it
Synopsis
Start work on an issue: name its branch the way the interface does — from the issue’s type and summary — then create it off the current branch’s base and switch to it, which moves the working tree onto the new branch. A preview is printed and confirmed before anything is created.
–fetch fetches the base remote first — upstream in a fork’s clone, else origin — so the branch starts from what it holds now; a fetch that fails creates nothing. –worktree creates the branch in a new worktree beside the repository instead, leaving this checkout where it is, and prints the worktree’s directory alone on the last line.
workflow branch <issue> [flags]Examples
cd "$(workflow branch PROJ-7 --fetch --worktree --yes | tail -n 1)" # start fresh, beside this checkoutOptions
--fetch[=true|false] fetch the base remote first (upstream in a fork's clone, else origin), to start from what it holds now
-h, --help[=true|false] help for branch
--worktree[=true|false] create the branch in a new worktree beside the repository, and print its directory
-y, --yes[=true|false] go ahead without the confirmationOptions inherited from parent commands
-n, --dry-run[=true|false] hold back every write to Jira, the forge, the messaging service, Taskwarrior, git and files, and say what it would have done
--log-format FORMAT say what goes to stderr as FORMAT: text, or json or logfmt, an entry a line stamped with its time (default text)
-q, --quiet[=true|false] say only warnings, errors and questions on stderr, leaving every note out
--request-log FILE append a one-line outline of each request (method, path, status, duration) to FILE, for a bug report
--verbose[=true|false] also say each request's outline on stderr, as a debug line (not while the terminal interface draws)SEE ALSO
- workflow - Run your Jira, Git forge and messaging workflow, in the terminal or a browser