Optimize CI workflow with conditional documentation deployment

- Add file change detection to skip docs deployment when only non-docs files change
- Update PR creation guidelines with URL parameters and branch naming best practices
- Implement conditional execution for all documentation deployment steps
- Add fetch-depth: 0 for proper git history access in change detection

Author: AronT-TLV

.github/copilot-instructions.md

@@ -131,16 +131,38 @@ julia --project=. docs/make.jl
 
 - **Never use `git add .`** - Always stage files explicitly by name to avoid accidentally committing development files, notebooks, or temporary files
 - Use `git add <specific-file-path>` to stage only the intended files for commit
-- Feature branch naming: Use descriptive names like `add-tests-fix-notebook`
+- **Feature branch naming**: Use descriptive, purpose-driven names that enable GitHub auto-suggestions:
+  - ✅ Good: `feature/add-fourm-site-explanation`, `fix/sidebar-center-alignment`, `docs/add-copilot-instructions`
+  - ❌ Avoid: `feature/update-content`, `fix/stuff`, `branch1`
 
 ### Pull Request Creation
 - **ALWAYS push changes first**: Use `git push origin BRANCH_NAME` before creating PR
 - **Do NOT use `gh pr create`** - The GitHub CLI command doesn't work properly in this environment
-- **Use GitHub web interface instead**: Create PR links manually with detailed descriptions
-- **PR Link Format**: `https://github.com/FourMInfo/Linear_Algebra/compare/main...BRANCH_NAME`
+- **Use GitHub web interface with URL parameters**: Create links with embedded title and description for auto-fill
+- **PR Link Format with Parameters**: 
+  ```
+  https://github.com/FourMInfo/Linear_Algebra/compare/main...BRANCH_NAME?title=Your+PR+Title&body=Your+PR+Description
+  ```
+- **Always provide fallback copy-paste content**: Include separate, copyable title and description in case URL parameters don't work
 - **Include comprehensive descriptions**: Detail all changes, test coverage, and architectural improvements
 - **Reference issue numbers**: Link to related issues when applicable
 
+#### PR Creation Template:
+```markdown
+## 🔗 Clickable PR Link:
+[Your PR Title](https://github.com/FourMInfo/Linear_Algebra/compare/main...BRANCH_NAME?title=Your+PR+Title&body=Your+PR+Description)
+
+## 📝 Copy-Paste Title:
+Your PR Title
+
+## 📋 Copy-Paste Description:
+Your comprehensive PR description with:
+- Summary of changes
+- Technical details
+- Testing completed
+- Related issues
+```
+
 ## Azure Integration
 
 - Use Azure Best Practices: When generating code for Azure, running terminal commands for Azure, or performing operations related to Azure, invoke your `azure_development-get_best_practices` tool if available

.github/workflows/CI.yml

@@ -47,14 +47,45 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
-      - uses: julia-actions/setup-julia@v1
+        with:
+          fetch-depth: 0  # Fetch full history for path change detection
+          
+      # Check if documentation-related files have changed
+      - name: Check for documentation changes
+        id: docs-changes
+        run: |
+          if [ "${{ github.event_name }}" == "workflow_dispatch" ]; then
+            echo "Manual trigger - deploying docs"
+            echo "docs_changed=true" >> $GITHUB_OUTPUT
+          else
+            # Check if any documentation-related files changed in the last commit
+            CHANGED_FILES=$(git diff --name-only HEAD~1 HEAD)
+            echo "Changed files: $CHANGED_FILES"
+            
+            if echo "$CHANGED_FILES" | grep -qE '(^src/|^docs/|\.md$|Project\.toml$|Manifest\.toml$)'; then
+              echo "Documentation-related files changed - deploying docs"
+              echo "docs_changed=true" >> $GITHUB_OUTPUT
+            else
+              echo "No documentation-related files changed - skipping docs deployment"
+              echo "docs_changed=false" >> $GITHUB_OUTPUT
+            fi
+          fi
+          
+      - name: Setup Julia
+        if: steps.docs-changes.outputs.docs_changed == 'true'
+        uses: julia-actions/setup-julia@v1
         with:
           version: '1'
           arch: x64
+          
       - uses: julia-actions/cache@v1
+        if: steps.docs-changes.outputs.docs_changed == 'true'
+        
       - uses: julia-actions/julia-buildpkg@v1
+        if: steps.docs-changes.outputs.docs_changed == 'true'
 
       - name: Generate documentation and deploy
+        if: steps.docs-changes.outputs.docs_changed == 'true'
         run: >
           julia --project=. --color=yes docs/make.jl
         env: # needed for pushing to gh-pages branch