Merge branch 'main' into feature-ContentImages

Author: csharpfritz

.github/workflows/azure-dev.yml

@@ -36,8 +36,10 @@ jobs:
     steps:
       - name: Checkout
         uses: actions/checkout@v4
+
       - name: Install azd
         uses: Azure/setup-azd@v2
+
       - name: Setup .NET
         uses: actions/setup-dotnet@v4
         with:
@@ -52,10 +54,30 @@ jobs:
             --tenant-id "$Env:AZURE_TENANT_ID"
         shell: pwsh
 
-
       - name: Provision Infrastructure
         run: azd provision --no-prompt
 
       - name: Deploy Application
         run: azd deploy --no-prompt
-        
+
+      - name: Refresh Web App Cache
+        if: success()
+        run: |
+          echo "Refreshing web application cache..."
+          # Wait a moment for the deployment to fully complete
+          sleep 5
+          
+          # Call the cache refresh endpoint with API key authentication
+          response=$(curl -s -w "%{http_code}" -X POST "https://copilotthatjawn.com/api/cache/refresh" \
+            -H "X-API-Key: ${{ secrets.CACHE_REFRESH_API_KEY }}" \
+            -o /tmp/cache_response.json)
+          
+          if [ "$response" = "200" ]; then
+            echo "Cache refresh successful"
+            cat /tmp/cache_response.json
+          else
+            echo "Cache refresh failed with HTTP status: $response"
+            cat /tmp/cache_response.json || echo "No response body"
+            # Don't fail the workflow if cache refresh fails - it's not critical
+            echo "Continuing workflow despite cache refresh failure..."
+          fi

.github/workflows/cleanup-container-images.yml

@@ -66,12 +66,14 @@ jobs:
           fi
 
       - name: Cleanup Old Container Images
+        id: cleanup
         run: |
           acr_name="${{ steps.get-acr.outputs.acr_name }}"
           dry_run="${{ github.event.inputs.dry_run || 'false' }}"
           
           if [ -z "$acr_name" ]; then
             echo "No Azure Container Registry found. Skipping cleanup."
+            echo "purged_count=0" >> $GITHUB_OUTPUT
             exit 0
           fi
           
@@ -83,6 +85,7 @@ jobs:
           
           if [ -z "$repositories" ]; then
             echo "No repositories found in ACR. Nothing to clean up."
+            echo "purged_count=0" >> $GITHUB_OUTPUT
             exit 0
           fi
           
@@ -94,7 +97,7 @@ jobs:
             PURGE_FILTERS="$PURGE_FILTERS --filter '$repo:.*'"
           done
           
-          # Construct the purge command
+          # Construct the purge command and capture the output
           PURGE_CMD="acr purge $PURGE_FILTERS --ago 0d --keep 5 --untagged"
           
           if [ "$dry_run" = "true" ]; then
@@ -103,18 +106,41 @@ jobs:
           fi
           
           echo "Running purge command..."
-          # Set longer timeout (1 hour) for large registries
-          az acr run \
+          # Run the purge command and capture output
+          purge_output=$(az acr run \
             --cmd "$PURGE_CMD" \
             --registry "$acr_name" \
             --timeout 3600 \
-            /dev/null
+            /dev/null)
           
           exit_code=$?
+            # Count purged images by looking for lines with "Deleted manifest" in the output
+          purged_count=$(echo "$purge_output" | grep -c "Deleted manifest" || true)
+          echo "purged_count=$purged_count" >> $GITHUB_OUTPUT
           
           if [ $exit_code -eq 0 ]; then
             echo "✅ Cleanup process completed successfully!"
+            echo "🧹 Images purged: $purged_count"
           else
             echo "❌ Cleanup process failed with exit code $exit_code"
             exit $exit_code
-          fi
+          fi
+      
+      - name: Create Summary
+        run: |
+          purged_count="${{ steps.cleanup.outputs.purged_count }}"
+          dry_run="${{ github.event.inputs.dry_run || 'false' }}"
+          
+          echo "## Container Registry Cleanup Summary" >> $GITHUB_STEP_SUMMARY
+          echo "- Registry: \`${{ steps.get-acr.outputs.acr_name }}\`" >> $GITHUB_STEP_SUMMARY
+          echo "- Date: $(date -u '+%Y-%m-%d %H:%M:%S UTC')" >> $GITHUB_STEP_SUMMARY
+          
+          if [ "$dry_run" = "true" ]; then
+            echo "- Mode: 🔍 **DRY RUN** (no images were actually deleted)" >> $GITHUB_STEP_SUMMARY
+            echo "- Images that would be purged: **$purged_count**" >> $GITHUB_STEP_SUMMARY
+          else
+            echo "- Mode: ✅ **Production Run**" >> $GITHUB_STEP_SUMMARY
+            echo "- Images purged: **$purged_count**" >> $GITHUB_STEP_SUMMARY
+          fi
+          
+          echo "- Retention Policy: Keep 5 most recent images per repository" >> $GITHUB_STEP_SUMMARY

.github/workflows/content-sync.yml

@@ -27,17 +27,38 @@ jobs:
       - uses: actions/setup-dotnet@v4
         with:
           dotnet-version: '9.0.x'
+      
+      - name: Cache NuGet packages
+        uses: actions/cache@v4
+        with:
+          path: ~/.nuget/packages
+          key: ${{ runner.os }}-nuget-${{ hashFiles('**/*.csproj', '**/packages.lock.json') }}
+          restore-keys: |
+            ${{ runner.os }}-nuget-
+      
+      - name: Cache .NET build outputs
+        uses: actions/cache@v4
+        with:
+          path: |
+            **/bin
+            **/obj
+          key: ${{ runner.os }}-dotnet-build-${{ hashFiles('**/*.csproj', '**/*.cs', '**/Program.cs') }}
+          restore-keys: |
+            ${{ runner.os }}-dotnet-build-
+      
+      - name: Restore dependencies
+        run: dotnet restore ContentLoader/ContentLoader.csproj
 
       - name: Build ContentLoader
-        run: dotnet build ContentLoader/ContentLoader.csproj --configuration Release
+        run: dotnet build ContentLoader/ContentLoader.csproj --configuration Release --no-restore
 
       - name: Upload Content
         id: upload-content
         env:
           AZURE_STORAGE_CONNECTION_STRING: ${{ secrets.CONTENT_STORAGE_CONNECTION_STRING }}
         run: |
           # Capture the output from the ContentLoader
-          output=$(dotnet run --project ContentLoader/ContentLoader.csproj --configuration Release -- Content 2>&1)
+          output=$(dotnet run --project ContentLoader/ContentLoader.csproj --configuration Release --no-build -- Content 2>&1)
           echo "$output"          # Extract sync summary numbers using awk for more reliable parsing
           added=$(echo "$output" | awk '/Added:/ {print $2}')
           updated=$(echo "$output" | awk '/Updated:/ {print $2}')

Content/Tips/copilot-checklist-interviewer.md

@@ -0,0 +1,52 @@
+---
+title: "Use Copilot as Your Personal Checklist and Interviewer"
+description: "Learn how to leverage Copilot to generate step-by-step checklists and interview you through complex processes for better productivity and organization."
+category: "Productivity"
+tags: ["copilot", "productivity", "workflow", "checklist", "process"]
+difficulty: "Beginner"
+datePublished: "2025-06-17"
+author: "Copilot That Jawn"
+featured: false
+---
+
+One powerful way to boost your productivity with Copilot is to ask it to generate a checklist or to interview you step-by-step for a task. Instead of just requesting information or a solution, try prompts like:
+
+- "Give me a checklist for launching a new product."
+- "Interview me to gather requirements for a client presentation."
+- "Walk me through the steps to plan a successful team meeting."
+- "Create a project management checklist for my team."
+- "Help me plan a budget proposal by asking me questions."
+
+## Why This Works
+
+Copilot will respond with a structured list or a series of questions, helping you:
+
+- **Clarify your process** - Break down complex tasks into manageable steps
+- **Avoid missing steps** - Ensure nothing falls through the cracks
+- **Stay organized** - Follow a logical sequence of actions
+- **Learn best practices** - Discover industry-standard approaches
+- **Document your workflow** - Create reusable processes for your team
+
+## Example in Action
+
+**Your Prompt:** "Interview me to gather requirements for planning a company event."
+
+**Copilot's Response:**
+
+1. What type of event are you planning (conference, celebration, training, etc.)?
+2. How many attendees are you expecting?
+3. What's your budget range for this event?
+4. Do you have a preferred date or timeline?
+5. What are your venue requirements (location, capacity, amenities)?
+6. Are there any special accommodations or accessibility needs?
+
+## Pro Tips
+
+- **After Copilot generates a checklist**, you can ask it to expand on any step, provide additional resources, or even help you create action items for each step
+- **Use follow-up questions** like "What's the best practice for step 3?" or "Can you give me a template for step 5?"
+- **Save successful checklists** as templates for future projects
+- **Use your microphone and dictation** - Instead of typing long responses to Copilot's interview questions, use voice input to speak your thoughts naturally. This makes the conversation flow more like a real consultation and helps you articulate ideas quickly without getting bogged down in typing
+- **Think out loud with voice** - When Copilot asks clarifying questions, use voice dictation to brainstorm and explore ideas verbally. You can refine and edit afterward, but speaking helps you capture thoughts faster than typing
+- **Treat Copilot like a collaborative partner** - let it guide you, ask follow-up questions, and help you think through your work like a seasoned professional
+
+This approach is especially useful for complex workflows, onboarding new team members, project planning, event management, or when you want to ensure best practices are followed consistently across your organization.