Add documentation for resolving GitHub CodeQL analysis configuration error. Update active context and progress tracking notes to reflect changes.

Author: mattmattox

docs/github-codeql-fix.md

@@ -0,0 +1,46 @@
+# Fixing CodeQL Analysis Configuration Error
+
+## Problem
+
+GitHub is reporting the following error when attempting to process CodeQL analysis:
+
+```
+Code Scanning could not process the submitted SARIF file: CodeQL analyses from advanced configurations cannot be processed when the default setup is enabled
+```
+
+This error occurs because there is a conflict between:
+
+1. **GitHub's Default CodeQL Setup** (enabled in repository settings)
+2. **Custom CodeQL Workflow** (defined in `.github/workflows/codeql.yml`)
+
+GitHub does not support running both configurations simultaneously for the same language.
+
+## Solution
+
+Disable the default CodeQL setup in GitHub repository settings to allow your custom workflow to run properly:
+
+1. Navigate to your GitHub repository
+2. Go to **Settings** > **Code security and analysis**
+3. Find the **Code scanning** section
+4. Click the **Configure** or **Disable** button next to "Default setup"
+5. Select **Disable default setup**
+6. Save your changes
+
+Your custom CodeQL workflow (`.github/workflows/codeql.yml`) will now run without conflicts with the default setup.
+
+## Why This Approach?
+
+The custom workflow is preferred because:
+
+1. It provides more control over the scanning configuration
+2. It can be version controlled along with your codebase
+3. It integrates better with your existing CI/CD pipeline
+4. It can be customized for your specific Go codebase needs
+
+## Custom Workflow Details
+
+Your current custom CodeQL workflow:
+- Runs on pushes to main, pull requests to main, and weekly (Sunday at midnight)
+- Analyzes Go language code
+- Uses the latest CodeQL action (v3)
+- Has appropriate permissions for security event writing

memory-bank/activeContext.md

@@ -4,6 +4,7 @@
 - **Cilium Troubleshooting Guide Update**: Created new in-depth guide for 2025 with advanced troubleshooting techniques
 - **Social Media Content**: Developed BlueSky and LinkedIn posts to promote the new guide
 - **Memory Bank Setup**: Established documentation structure for future work continuity
+- **GitHub CodeQL Fix**: Resolved code scanning configuration conflict
 
 ## Recent Changes
 1. Created comprehensive `cilium-troubleshooting-2025.md` blog post with expanded content:
@@ -20,15 +21,22 @@
 
 3. Established Memory Bank documentation to maintain project continuity
 
+4. Fixed GitHub CodeQL configuration issue:
+   - Documented conflict between default and custom CodeQL setups
+   - Created documentation explaining the root cause and solution
+   - Created `docs/github-codeql-fix.md` with detailed steps to resolve the issue
+
 ## Active Decisions and Considerations
 - **Content Organization**: Kept blog posts in the main blog directory while organizing social media content in dedicated subdirectories (`social-media-post/cilium-troubleshooting-2025/`)
 - **Emoji Usage**: Selected technical and problem-solving themed emojis for social posts to increase engagement
 - **Technical Depth**: Emphasized advanced troubleshooting techniques over basic concepts to provide unique value
 - **Social Media Structure**: Differentiated BlueSky (shorter, more casual) from LinkedIn (longer, more professional) content styles
 - **Memory Bank Structure**: Implemented complete documentation structure for future reference
+- **CodeQL Configuration**: Prioritized custom workflow over default setup for better control and integration with CI/CD pipeline
 
 ## Next Steps
 1. Consider setting up an image directory for blog post diagrams at `cdn.support.tools/posts/cilium-troubleshooting-2025/`
 2. Evaluate metrics to track engagement with the new blog post
 3. Explore additional social media platforms for content promotion
 4. Identify follow-up topics that could complement the Cilium troubleshooting guide
+5. Implement the recommended GitHub CodeQL fix to resolve the code scanning issue

memory-bank/progress.md

@@ -7,6 +7,7 @@
 - **Documentation**: Established complete Memory Bank structure for project continuity
 - **Deployment Pipeline**: ArgoCD configuration suggests functioning GitOps deployment
 - **CDN Configuration**: External asset hosting appears to be configured correctly
+- **Technical Documentation**: Created documentation for resolving GitHub CodeQL configuration issues
 
 ## What's Left to Build
 - **Image Resources**: Need to create/update diagrams for the Cilium troubleshooting guide
@@ -22,9 +23,10 @@
 - **Content Organization**: Complete - blog posts in main blog directory with social media in dedicated subdirectories
 - **CDN Resources**: Pending - need to evaluate if additional images are needed
 - **Deployment**: Pending - new content ready for deployment process
+- **GitHub CodeQL**: Documented solution - created guidance on fixing the configuration conflict
 
 ## Known Issues
-- No specific technical issues identified in the current work
+- GitHub CodeQL scanning reporting configuration conflict - solution documented in `docs/github-codeql-fix.md`
 - Need to verify how images are referenced in blog posts to ensure CDN paths are correct
 - May need to test if the social media post formatting displays correctly on actual platforms
 - Should confirm that 2025 publication date functions correctly with the Hugo platform