diff --git a/scripts/ci/jobs/pre-commit.yml b/scripts/ci/jobs/pre-commit.yml
index eabca775316..d2dfb72bfdc 100644
--- a/scripts/ci/jobs/pre-commit.yml
+++ b/scripts/ci/jobs/pre-commit.yml
@@ -14,6 +14,8 @@ clang-format:
   stage: check
   image: $PRECOMMIT_IMAGE
   rules:
+    - if: $CI_MERGE_REQUEST_LABELS =~ /.*ci::web only \(fast.*/
+      when: never
     - if: $CI_MERGE_REQUEST_IID
   needs: [ci_images]
   script:
diff --git a/web/content/docs/devguide/advanced/vscode-debugging/index.md b/web/content/docs/devguide/advanced/vscode-debugging/index.md
new file mode 100644
index 00000000000..879df7bfa30
--- /dev/null
+++ b/web/content/docs/devguide/advanced/vscode-debugging/index.md
@@ -0,0 +1,56 @@
++++
+date = "2014-09-12T11:00:13+01:00"
+title = "Debugging in VS Code"
+author = "Lars Bilke"
+weight = 1062
+
+[menu]
+  [menu.devguide]
+    parent = "advanced"
++++
+
+<div class="note">
+<i class="far fa-exclamation-triangle"></i> This guide applies to Linux-only!
+</div>
+
+[Visual Studio Code](https://code.visualstudio.com/) is a powerful text editor which can be expanded to a full featured integrated development environment (IDE) with plugins. To debug a program make sure to install the [C/C++ Extension Pack](https://marketplace.visualstudio.com/items?itemName=ms-vscode.cpptools-extension-pack) which includes support for CMake and debugging with `gdb`.
+
+Then in the editor:
+
+1. Open e.g. `ogs.cpp`.
+2. Set a [breakpoint](https://code.visualstudio.com/docs/editor/debugging#_breakpoints) in the first line of the `main()`-function (around line 58) by clicking on the left gutter in the editor window (a red dot marks the enabled breakpoint).
+3. Click on the `CMake`-sidebar.
+4. Make sure that `debug` is the active configure and build preset.
+5. Click the `Build`-button in the status bar.
+6. Click the bug icon in the status bar.
+
+![Initiate debug session](vscode-debugging-1.png)
+
+After some seconds the debugger starts and halts at the specified breakpoint indicated y the yellow marker around the breakpoint and line. You can now step into or over statements with debugger controls at the top of the window:
+
+![Running debug session](vscode-debugging-2.png)
+
+To debug with specific arguments to `ogs`, e.g. for setting a `.prj`-file:
+
+1. Click on the `Debug`-sidebar.
+2. Click on `create a launch.json file`.
+3. Click `Add Configuration`.
+4. Select `C/C++: (gdb) Launch`
+
+![Setup a launch.json file](vscode-debugging-3.png)
+
+Edit the file e.g. like this:
+
+```json
+"program": "${workspaceFolder}/../build/debug/bin/ogs",
+"args": ["${workspaceFolder}/Tests/Data/Parabolic/ComponentTransport/ReactiveTransport/CO2Injection/cl.prj"],
+"cwd": "${workspaceFolder}/../build/debug/_out",
+```
+
+This sets the program to debug to the `ogs`-binary in the debug build folder, sets a specific `.prj`-file to run and sets the working directory (output folder) to some `_out`-subfolder in the build directory.
+
+You can also give the debug configuration some meaningful name, e.g. `"name": "Debug cl.prj",` which results in a new button in the status bar:
+
+![Debug button](vscode-debugging-4.png)
+
+Click on it to start the debug session.
diff --git a/web/content/docs/devguide/advanced/vscode-debugging/vscode-debugging-1.png b/web/content/docs/devguide/advanced/vscode-debugging/vscode-debugging-1.png
new file mode 100644
index 00000000000..f266c39a36f
Binary files /dev/null and b/web/content/docs/devguide/advanced/vscode-debugging/vscode-debugging-1.png differ
diff --git a/web/content/docs/devguide/advanced/vscode-debugging/vscode-debugging-2.png b/web/content/docs/devguide/advanced/vscode-debugging/vscode-debugging-2.png
new file mode 100644
index 00000000000..3b20ad44d9c
Binary files /dev/null and b/web/content/docs/devguide/advanced/vscode-debugging/vscode-debugging-2.png differ
diff --git a/web/content/docs/devguide/advanced/vscode-debugging/vscode-debugging-3.png b/web/content/docs/devguide/advanced/vscode-debugging/vscode-debugging-3.png
new file mode 100644
index 00000000000..c5a10f3fce6
Binary files /dev/null and b/web/content/docs/devguide/advanced/vscode-debugging/vscode-debugging-3.png differ
diff --git a/web/content/docs/devguide/advanced/vscode-debugging/vscode-debugging-4.png b/web/content/docs/devguide/advanced/vscode-debugging/vscode-debugging-4.png
new file mode 100644
index 00000000000..d0fc3bdd6da
Binary files /dev/null and b/web/content/docs/devguide/advanced/vscode-debugging/vscode-debugging-4.png differ