Add 'TEST' section to examples documentation

.github/workflows/pr-checks.yml

@@ -34,8 +34,19 @@ jobs:
       - name: Check for code changes
         id: check_files
         run: |
+          set -ex # Exit on error, print commands for debugging
+
           echo "Checking for code changes..."
-          CHANGED_FILES=$(git diff --name-only ${{ github.event.pull_request.base.sha }}...${{ github.event.pull_request.head.sha }})
+          # Diff the current PR branch HEAD against the TARGET branch's HEAD
+          # The '...' syntax finds the common ancestor and diffs from there.
+          CHANGED_FILES=$(git diff --name-only origin/${{ github.base_ref }}...HEAD)
+
+          if [[ -z "$CHANGED_FILES" ]]; then
+            echo "No changed files found. Assuming no code changes."
+            echo "has_code_changes=false" >> $GITHUB_OUTPUT
+            exit 0
+          fi
+
           echo "Files changed in this PR:"
           echo "$CHANGED_FILES"
           NON_DOC_FILES=$(echo "$CHANGED_FILES" | grep -vE '(\.md|\.txt)$|^docs/')

app/app_test.go

@@ -13,6 +13,7 @@ import (
 )
 
 func TestApplicationFileProcessor(t *testing.T) {
+	// TEST COMMENTS
 	ctx := context.Background()
 	cmd := &cobra.Command{}
 	app := New(ctx, cmd)

docs/configuration.md

@@ -1,5 +1,5 @@
 # Configuration File
-
+TEST
 The configuration file can be a `TOML`, `YAML` or `JSON` file. By default, `immich-go` looks for a file named `immich-go.toml` in the current directory.
 
 ## Configuration file structure

docs/examples.md

@@ -1,5 +1,6 @@
 # Examples and Use Cases
 
+TEST
 This guide provides practical examples for common Immich-Go scenarios.
 
 ## Quick Reference