Search “git-for-each-ref” — BetterMan

Search

Tip: Use ssh_config or systemd.unit for dotted names.

Did you mean: git-for-each-repo, git-check-ref-format, git-refs, git-show-ref?

Output information on each ref

NAME git-for-each-ref - Output information on each ref SYNOPSIS git for-each-ref

git-branch(1)

List, create, or delete branches

same as that of git-for-each-ref (1). CONFIGURATION pager.branch is only respected when ... used as the default. See git-for-each-ref (1) field names for valid values

git-show-ref(1)

List references in a local repository

FILES .git/refs/* , .git/packed-refs SEE ALSO git-for-each-ref (1), git-ls-remote (1), git

git-ls-remote(1)

List references in a remote repository

versionsort.suffix" configuration variable. See git-for-each-ref (1) for more sort options

git(1)

the stupid content tracker

found via two tree objects. git-for-each-ref (1) Output information on each ref

git-tag(1)

Create, list, delete or verify a tag object signed with GPG

same as that of git-for-each-ref (1). When unspecified, defaults to %(refname:strip

git-config(1)

Get and set repository or global options

used as the default. See git-for-each-ref (1) field names for valid values ... specified command instead of git-for-each-ref (1). The first argument is the absolute

git-for-each-repo(1)
Run a Git command on a list of repositories
```
NAME git-for
```
git-check-ref-format(1)
Ensures that a reference name is well formed
```
NAME git-check
```
git-refs(1)
Low-level access to refs
```
NAME git-refs
```
git-reflog(1)
Manage reflog information
```
NAME git-reflog
```
git-update-ref(1)
Update the object name stored in a ref safely
```
NAME git-update
```
git-format-patch(1)
Prepare patches for e-mail submission
```
NAME git-format
```
git-symbolic-ref(1)
Read, modify and delete symbolic refs
```
NAME git-symbolic
```
git-rerere(1)
Reuse recorded resolution of conflicted merges
```
NAME git-rerere
```

15 results loaded