As mentioned in comments to Mark Adelsberger’s answer, this was a default behavior change introduced in Git 2.16.
You can turn paged output for git branch
back off by default with the pager.branch
config setting:
git config --global pager.branch false
More Related Contents:
- How to clone all remote branches in Git
- Branch from a previous commit using Git
- How to replace master branch in Git, entirely, from another branch? [duplicate]
- Modified files in a git branch are spilling over into another branch
- Can I recover a branch after its deletion in Git?
- Default behavior of “git push” without a branch specified
- What is the difference between origin and upstream on GitHub?
- Why does git perform fast-forward merges by default?
- Deleting a badly named git branch
- Rename master branch for both local and remote Git repositories
- Create a branch in Git from another branch
- How do I copy a version of a single file from one Git branch to another?
- fetch in git doesn’t get all branches
- How do I rename both a Git local and remote branch name?
- Move branch pointer to different commit without checkout
- Is there a way to lock a branch in GIT
- How do I get the current branch name in Git?
- How do I create a remote Git branch?
- What are the differences between local branch, local tracking branch, remote branch and remote tracking branch?
- How do I commit only some files?
- How to exit a ‘git status’ list in a terminal?
- What is the difference between “git branch” and “git checkout -b”?
- List Git aliases
- Git submodule to track remote branch
- git switch branch without discarding local changes
- git how to find commit hash where branch originated from
- Update Git branches from master
- Git remote branch deleted, but still it appears in ‘branch -a’
- How do I list all remote branches in Git 1.7+?
- Why call git branch –unset-upstream to fixup?