mermaid

Author: sharpchen

docs/document/Skill/Git/docs/4.Git History & Reset.md

@@ -38,25 +38,30 @@ $ git log master..pwsh_es
 
 ## Bisect
 
-`git bisect` is a subcommand to search a target commit by testing *good* or *bad*, which delineated a range of the possible target commit, and you keep half-cut the range by testing *good* or *bad* until you met both *good* which means your found the target.
+`git bisect` is a subcommand to search a target commit by testing *good* or *bad*, which delineated a range of the possible target commit, and you keep half-cut the range by testing *good* or *bad* until you met the final commit that's *bad*.
 
 Assuming you have a error one testing introduced at some point but you can't figure out which commit introduced it, but you are dare to stride back to a commit that does not error which can be a start point of *good*.
 Correspondingly, the current commit you're on can be the start point of *bad*, that is, the error was introduced between *good* and *bad*.
 
 ```mermaid
+---
+config:
+  logLevel: 'debug'
+  theme: 'base'
+---
 gitGraph
     commit
     commit
     commit
-    commit id: 'good' tag: 'test passed'
+    commit tag: 'good' id: 'test passed'
     commit
     commit
     commit
-    commit tag: 'might be target'
+    commit tag: 'might be target between'
     commit
     commit
     commit
-    commit id: 'bad' tag: 'test failed'
+commit tag: 'bad' id: 'test failed'
 ```
 
 1. `git bisect start`: enter *bisect* stage

package.json

@@ -20,7 +20,7 @@
     "@types/node": "^20.14.5",
     "axios": "^1.7.2",
     "jsonc-parser": "^3.2.1",
-    "mermaid": "^10.9.1",
+    "mermaid": "11.7.0",
     "shiki": "^1.7.0",
     "typescript": "^5.6.3",
     "vitepress": "latest",