Test

docs/configuration.md

@@ -17,6 +17,10 @@ To fail the workflow on broken links, enable strict mode in one of two ways:
 
 **Repository secret (recommended for gradual rollout):**
 
+[Testlink](newfile.md)
+
+[Another testlink](/test-folder/testfile.md)
+
 Go to **Settings > Secrets and variables > Actions** and create a secret named `LINK_CHECK_STRICT` with the value `true`. Then pass it in the workflow:
 
 ```yaml
@@ -57,3 +61,6 @@ Common use cases:
 On pull requests, only changed files are scanned. Broken links in files that are not part of the diff are reported as check annotations rather than inline comments.
 
 The following directories are always excluded from scanning: `node_modules/`, `.git/`, `dist/`, `lib/`.
+
+
+

docs/newfile.md

@@ -0,0 +1 @@
+Bla

test-folder/testfile.md

@@ -0,0 +1,9 @@
+This is a new file.
+
+[Link to other file](/docs/newfile.md)
+
+Another link, but slightly wrong! :-)
+
+[Incorrect link to other file](/docs/newfile.md)
+
+And let's see what happens if they are both on the same line. [Link to other file](/docs/newfile.md) [Incorrect link to other file](/docs/newfile.md)