usage: git line <command>

Shows basic help, the current git-line version, and read-only insights for the current branch.
When the current branch was created from another branch and that base branch has new commits,
Git Line recommends `git line update`.
Use `git line help` or `git line -h` for the same basic help, and `git line --version` for only the version.
Git reserves `git line --help` for manual pages, so inline help uses `git line help` instead.

usage: git line start <branch_name> [--from <base_branch>|--from-here]

Creates a feature branch starting from <base_branch>, the current branch with `--from-here`,
or DEVELOPMENT_BRANCH when omitted.
The generated branch name includes the short base branch name: `from-<short_base_branch>/<branch_name>`,
or `<prefix>/from-<short_base_branch>/<branch_name>` when branch prefixes are enabled.
For a base branch with slashes, the short base branch name is its final path component.
Spaces in generated branch name components are converted to hyphens.

usage: git line commit

Commit all changes with a commit message.
Creates an additional empty commit if its the first commit on the branch. This is useful to force Github to use the PR title when using "Squash and merge".

usage: git line push

Push the current branch and set an upstream if needed.

usage: git line stash

Stash tracked and untracked changes.

usage: git line switch [<partial_branch_name>]

Checks out an exact or partial local branch match, or lists recent branches for selection when no name is provided.
Exact branch name matches are selected before partial matches.

usage: git line edit 

Interactive rebase with autosquash to current branch's oldest ancestor from DEVELOPMENT_BRANCH.

usage: git line update 

Updates the current branch's base from its configured upstream, then rebases current branch onto it.
For branches created by `git line start`, the base comes from the branch's git-line base configuration,
with the generated `from-<base_branch>` branch name used as a fallback for older branches.
Branches without a generated base use DEVELOPMENT_BRANCH.

usage: git line unstack [<base_branch>]

Moves the current branch from its git-line base onto <base_branch>, or DEVELOPMENT_BRANCH when omitted.
This is useful after a stacked branch's base has been merged and the current branch should be rebased
directly onto the development branch.
Internally this uses `git rebase --onto <base_branch> <old_base_branch>`, so only commits unique to
the current branch are replayed. After a successful rebase, Git Line updates the branch's stored base.
The current branch name and upstream configuration are left unchanged so existing pull requests keep
tracking the same branch.

usage: git line squash [<commit_message>]

Squash all commits of current branch into one. It will not apply to branches listed in PROTECTED_BRANCHES.

usage: git line remove

Removes current branch locally and from origin. It will not apply to branches listed in PROTECTED_BRANCHES.

usage: git line nuke

Remove all remote branches removed from origin and all local branches which remote is gone. It will not remove branches which never had remotes.