Use four dashes to wrap code snippets accordingly to AsciiDoc format

Author: Morganov

book/07-git-tools/sections/credentials.asc

@@ -164,9 +164,9 @@ Once again, we'll write this extension in Ruby, but any language will work so lo
 Here's the full source code of our new credential helper:
 
 [source,ruby]
---------
+----
 include::../git-credential-read-only[]
---------
+----
 
 <1> Here we parse the command-line options, allowing the user to specify the input file.
     The default is `~/.git-credentials`.

book/07-git-tools/sections/signing.asc

@@ -51,7 +51,7 @@ user: "Ben Straub <[email protected]>"
 If you run `git show` on that tag, you can see your GPG signature attached to it:
 
 [source,console]
---------
+----
 $ git show v1.5
 tag v1.5
 Tagger: Ben Straub <[email protected]>
@@ -75,7 +75,7 @@ Author: Scott Chacon <[email protected]>
 Date:   Mon Mar 17 21:52:11 2008 -0700
 
     Change version number
---------
+----
 
 ==== Verifying Tags
 

book/A-git-in-other-environments/sections/bash.asc

@@ -8,9 +8,9 @@ First, you need to get a copy of the `contrib/completion/git-completion.bash` fi
 Copy it somewhere handy, like your home directory, and add this to your `.bashrc`:
 
 [source,console]
------
+----
 . ~/git-completion.bash
------
+----
 
 Once that's done, change your directory to a Git repository, and type:
 
@@ -27,11 +27,11 @@ This can be as simple or complex as you want, but there are generally a few key
 To add these to your prompt, just copy the `contrib/completion/git-prompt.sh` file from Git's source repository to your home directory, add something like this to your `.bashrc`:
 
 [source,console]
------
+----
 . ~/git-prompt.sh
 export GIT_PS1_SHOWDIRTYSTATE=1
 export PS1='\w$(__git_ps1 " (%s)")\$ '
------
+----
 
 The `\w` means print the current working directory, the `\$` prints the `$` part of the prompt, and `__git_ps1 " (%s)"` calls the function provided by `git-prompt.sh` with a formatting argument.
 Now your bash prompt will look like this when you're anywhere inside a Git-controlled project:

book/A-git-in-other-environments/sections/guis.asc

@@ -43,9 +43,9 @@ In between is a collection of controls used for searching history.
 It, too, is easiest to invoke from the command line:
 
 [source,console]
------
+----
 $ git gui
------
+----
 
 And it looks something like this:
 

book/B-embedding-git/sections/dulwich.asc

@@ -11,7 +11,7 @@ Dulwich follows git design and separate two basic levels of API: plumbing and po
 Here is an example of using the lower level API to access the commit message of the last commit:
 
 [source, python]
------
+----
 from dulwich.repo import Repo
 r = Repo('.')
 r.head()
@@ -23,19 +23,19 @@ c
 
 c.message
 # 'Add note about encoding.\n'
------
+----
 
 To print a commit log using high-level porcelain API, one can use:
 
 [source, python]
------
+----
 from dulwich import porcelain
 porcelain.log('.', max_entries=1)
 
 #commit: 57fbe010446356833a6ad1600059d80b1e731e15
 #Author: Jelmer Vernooij <[email protected]>
 #Date:   Sat Apr 29 2017 23:57:34 +0000
------
+----
 
 
 ==== Further Reading

book/B-embedding-git/sections/go-git.asc

@@ -10,19 +10,19 @@ go-git is focused on extensibility, compatibility and supports most of the plumb
 Here is a basic example of using Go APIs:
 
 [source, go]
------
+----
 import "github.com/go-git/go-git/v5"
 
 r, err := git.PlainClone("/tmp/foo", false, &git.CloneOptions{
     URL:      "https://github.com/go-git/go-git",
     Progress: os.Stdout,
 })
------
+----
 
 As soon as you have a `Repository` instance, you can access information and perform mutations on it:
 
 [source, go]
------
+----
 // retrieves the branch pointed by HEAD
 ref, err := r.Head()
 
@@ -36,19 +36,19 @@ history, err := commit.History()
 for _, c := range history {
     fmt.Println(c)
 }
------
+----
 
 ==== Advanced Functionality
 
 go-git has few notable advanced features, one of which is a pluggable storage system, which is similar to Libgit2 backends.
 The default implementation is in-memory storage, which is very fast.
 
 [source, go]
------
+----
 r, err := git.Clone(memory.NewStorage(), nil, &git.CloneOptions{
     URL: "https://github.com/go-git/go-git",
 })
------
+----
 
 Pluggable storage provides many interesting options.
 For instance, https://github.com/go-git/go-git/tree/master/_examples/storage[] allows you to store references, objects, and configuration in an Aerospike database.
@@ -59,7 +59,7 @@ Using https://pkg.go.dev/github.com/go-git/go-billy/v5?tab=doc#Filesystem[] it i
 Another advanced use-case includes a fine-tunable HTTP client, such as the one found at https://github.com/go-git/go-git/blob/master/_examples/custom_http/main.go[].
 
 [source, go]
------
+----
 customClient := &http.Client{
     Transport: &http.Transport{ // accept any certificate (might be useful for testing)
         TLSClientConfig: &tls.Config{InsecureSkipVerify: true},
@@ -75,7 +75,7 @@ client.InstallProtocol("https", githttp.NewClient(customClient))
 
 // Clone repository using the new client if the protocol is https://
 r, err := git.Clone(memory.NewStorage(), nil, &git.CloneOptions{URL: url})
------
+----
 
 ==== Further Reading
 

book/B-embedding-git/sections/libgit2.asc

@@ -9,7 +9,7 @@ First, let's take a look at what the C API looks like.
 Here's a whirlwind tour:
 
 [source,c]
------
+----
 // Open a repository
 git_repository *repo;
 int error = git_repository_open(&repo, "/path/to/repository");
@@ -28,7 +28,7 @@ const git_oid *tree_id = git_commit_tree_id(commit);
 // Cleanup
 git_commit_free(commit);
 git_repository_free(repo);
------
+----
 
 The first couple of lines open a Git repository.
 The `git_repository` type represents a handle to a repository with a cache in memory.
@@ -194,9 +194,9 @@ The bindings are written in C#, and great care has been taken to wrap the raw Li
 Here's what our example program looks like:
 
 [source,csharp]
------
+----
 new Repository(@"C:\path\to\repo").Head.Tip.Message;
------
+----
 
 For desktop Windows applications, there's even a NuGet package that will help you get started quickly.
 
@@ -208,11 +208,11 @@ Objective-Git (https://github.com/libgit2/objective-git[]) is the name of the Li
 The example program looks like this:
 
 [source,objc]
------
+----
 GTRepository *repo =
     [[GTRepository alloc] initWithURL:[NSURL fileURLWithPath: @"/path/to/repo"] error:NULL];
 NSString *msg = [[[repo headReferenceWithError:NULL] resolvedTarget] message];
------
+----
 
 Objective-git is fully interoperable with Swift, so don't fear if you've left Objective-C behind.