Git

https://git-scm.com/docs
Admin
Git is a free and open-source distributed version control system designed to handle everything from...
Tokens:1,069,349
Snippets:10,185
Trust Score:9.8
Update:4 hours ago
Show doc for...
Tokens:
Raw
### Starting a bisection with example output

Source: https://git-scm.com/docs/git-bisect-lk2009

Example of starting a bisection with v2.6.27 as bad and v2.6.25 as good, showing the output with remaining revisions and the checked-out commit.

```bash
$ git bisect start v2.6.27 v2.6.25
Bisecting: 10928 revisions left to test after this (roughly 14 steps)
[2ec65f8b89ea003c27ff7723525a2ee335a2b393] x86: clean up using max_low_pfn on 32-bit
```

--------------------------------

### Git configuration file example

Source: https://git-scm.com/docs/git

Shows the text format for Git configuration files. Comments start with '#' or ';'. The example sets core.filemode to false and defines user identity with name and email.

```ini
#
# A '#' or ';' character indicates a comment.
#

; core variables
[core]
	; Don't trust file modes
	filemode = false

; user identity
[user]
	name = "Junio C Hamano"
	email = "gitster@pobox.com"

```

--------------------------------

### format string example output

Source: https://git-scm.com/docs/git-diff-tree

Example output of a format string using placeholders %h, %an, %ar, %n, %s.

```text
The author of fe6e0ee was Junio C Hamano, 23 hours ago
The title was >>t4119: test autocomputing -p<n> for traditional diff input.<<
```

--------------------------------

### Create example repositories for submodules

Source: https://git-scm.com/docs/user-manual

Creates four example repositories (a, b, c, d) in ~/git, each initialized with a text file and an initial commit. These repositories are later used as submodules.

```shell
$ mkdir ~/git
$ cd ~/git
$ for i in a b c d
do
	mkdir $i
	cd $i
	git init
	echo "module $i" > $i.txt
	git add $i.txt
	git commit -m "Initial commit, submodule $i"
	cd ..
done
```

--------------------------------

### Start a bisect session

Source: https://git-scm.com/docs/git-bisect/2.13.7

Example of starting a bisect session with a bad and good commit.

```console
$ git bisect start
$ git bisect bad                 # Current version is bad
$ git bisect good v2.6.13-rc2    # v2.6.13-rc2 is known to be good
```

--------------------------------

### Create a sample text file for hash generation

Source: https://git-scm.com/docs/user-manual

Creates a small text file with the content 'Hello world' to be used in the hash generation example.

```shell
$ echo "Hello world" >hello.txt

```

--------------------------------

### Start bisect with performance terms

Source: https://git-scm.com/docs/git-bisect/2.11.4

Example of starting a bisection with custom terms 'fast' and 'slow' to find a performance regression.

```shell
git bisect start --term-old fast --term-new slow

```

--------------------------------

### Create a new Git repository from scratch

Source: https://git-scm.com/docs/user-manual

Initializes a new repository in a fresh directory. Run mkdir, cd, and git init in sequence.

```shell
$ mkdir project
$ cd project
$ git init
```

--------------------------------

### Start bisection with performance terms

Source: https://git-scm.com/docs/git-bisect/2.13.7

Example of starting a bisection with custom terms 'fast' and 'slow' to find a performance regression.

```shell
git bisect start --term-old fast --term-new slow
```

--------------------------------

### Create tar.gz archive using builtin handling

Source: https://git-scm.com/docs/git-archive

Same as the previous example but uses the builtin tar.gz handling.

```shell
git archive --format=tar.gz --prefix=git-1.4.0/ v1.4.0 >git-1.4.0.tar.gz
```

--------------------------------

### Start bisection with bug-fix terms

Source: https://git-scm.com/docs/git-bisect/2.13.7

Example of starting a bisection with custom terms 'broken' and 'fixed' to find the commit that fixed a bug.

```shell
git bisect start --term-new fixed --term-old broken
```

--------------------------------

### Git config include and includeIf example

Source: https://git-scm.com/docs/git-config

A single comprehensive example from the Git documentation showing core, diff, branch, proxy, include, and includeIf configurations. It demonstrates absolute, relative, and ~ paths for includes, and conditions for gitdir, worktree, onbranch, and hasconfig. Note that hasconfig:remote.*.url can reference a URL defined later in the file.

```ini
# Core variables
[core]
	; Don't trust file modes
	filemode = false

# Our diff algorithm
[diff]
	external = /usr/local/bin/diff-wrapper
	renames = true

[branch "devel"]
	remote = origin
	merge = refs/heads/devel

# Proxy settings
[core]
	gitProxy="ssh" for "kernel.org"
	gitProxy=default-proxy ; for the rest

[include]
	path = /path/to/foo.inc ; include by absolute path
	path = foo.inc ; find "foo.inc" relative to the current file
	path = ~/foo.inc ; find "foo.inc" in your `$HOME` directory

; include if $GIT_DIR is /path/to/foo/.git
[includeIf "gitdir:/path/to/foo/.git"]
	path = /path/to/foo.inc

; include for all repositories inside /path/to/group
[includeIf "gitdir:/path/to/group/"]
	path = /path/to/foo.inc

; include for all repositories inside $HOME/to/group
[includeIf "gitdir:~/to/group/"]
	path = /path/to/foo.inc

; include if the worktree is at /path/to/project-build
[includeIf "worktree:/path/to/project-build"]
	path = build-config.inc

; include for all worktrees inside /path/to/group
[includeIf "worktree:/path/to/group/"]
	path = group-config.inc

; relative paths are always relative to the including
; file (if the condition is true); their location is not
; affected by the condition
[includeIf "gitdir:/path/to/group/"]
	path = foo.inc

; include only if we are in a worktree where foo-branch is
; currently checked out
[includeIf "onbranch:foo-branch"]
	path = foo.inc

; include only if a remote with the given URL exists (note
; that such a URL may be provided later in a file or in a
; file read after this file is read, as seen in this example)
[includeIf "hasconfig:remote.*.url:https://example.com/**"]
	path = foo.inc
[remote "origin"]
	url = https://example.com/git
```

--------------------------------

### Start bisect with bug fix terms

Source: https://git-scm.com/docs/git-bisect/2.11.4

Example of starting a bisection with custom terms 'fixed' and 'broken' to find the commit that fixed a bug.

```shell
git bisect start --term-new fixed --term-old broken

```

--------------------------------

### Sample .git/config file

Source: https://git-scm.com/docs/git-config

A sample configuration file showing comments, core variables, diff settings, proxy settings, and HTTP settings with URL-specific overrides.

```ini
#
# This is the config file, and
# a '#' or ';' character indicates
# a comment
#

; core variables
[core]
	; Don't trust file modes
	filemode = false

; Our diff algorithm
[diff]
	external = /usr/local/bin/diff-wrapper
	renames = true

; Proxy settings
[core]
	gitproxy=proxy-command for kernel.org
	gitproxy=default-proxy ; for all the rest

; HTTP
[http]
	sslVerify
[http "https://weak.example.com"]
	sslVerify = false
	cookieFile = /tmp/cookie.txt
```

--------------------------------

### Example of a folded trailer value

Source: https://git-scm.com/docs/git-interpret-trailers

Shows a trailer value split over multiple lines with continuation lines starting with whitespace.

```text
key: This is a very long value, with spaces and
  newlines in it.
```

--------------------------------

### Git config insteadOf example with multiple mappings

Source: https://git-scm.com/docs/git-clone/2.13.7

Example configuration that rewrites URLs like 'work:repo.git' or 'host.xz:/path/to/repo.git' to 'git://git.host.xz/repo.git'.

```ini
	[url "git://git.host.xz/"]
		insteadOf = host.xz:/path/to/
		insteadOf = work:

```

--------------------------------

### Create tar.gz archive with format inferred from output file

Source: https://git-scm.com/docs/git-archive

Same as the previous example, but the format is inferred from the output file extension.

```shell
git archive --prefix=git-1.4.0/ -o git-1.4.0.tar.gz v1.4.0
```

--------------------------------

### Rebase last 5 commits interactively

Source: https://git-scm.com/docs/git-rebase

Starts an interactive rebase on the last 5 commits, allowing you to reorder them. The example moves the first patch to the end of the list.

```bash
$ git rebase -i HEAD~5
```
Tokens:
Raw