Update CodeQL workflow to use Python language and remove init category

[a-ariff]

• Changed matrix.language from ['auto'] to ['python'] to specifically target Python code
• Removed category parameter from the Initialize CodeQL step
• Kept category parameter in the Perform CodeQL Analysis step for proper categorization

Pull Request Summary

Provide a brief description of the changes in this PR.

Type of Change

Please select the relevant option(s):

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update (changes to documentation only)
• Code refactoring (no functional changes, but improves code quality)
• Performance improvement
• Security fix
• Configuration change
• Other (please describe):

Related Issues

Closes #[issue number]
Fixes #[issue number]
Related to #[issue number]

Description

What does this PR do?

Provide a detailed description of the changes made in this pull request.

Why are these changes necessary?

Explain the problem this PR solves or the feature it adds.

How were these changes implemented?

Describe the approach taken to implement these changes.

Changes Made

PowerShell Scripts

• Modified existing scripts
• Added new scripts
• Removed scripts
• Updated script parameters
• Improved error handling
• Enhanced logging

Documentation

• Updated README.md
• Updated CONTRIBUTING.md
• Added inline code comments
• Updated parameter documentation
• Added usage examples

Configuration

• Modified configuration files
• Updated default settings
• Added new configuration options
• Removed deprecated settings

Testing

Test Environment

• PowerShell Version: [e.g., 5.1, 7.2, 7.3]
• Operating System: [e.g., Windows 10, Windows 11, Windows Server]
• Autotask Environment: [e.g., Production, Sandbox]

Testing Performed

• Unit testing completed
• Integration testing completed
• Manual testing completed
• Tested with multiple PowerShell versions
• Tested error handling scenarios
• Tested with different Autotask modules
• Performance testing completed

Test Cases

Describe the specific test cases that were executed:

1. Test Case 1: Description

   • Expected: What should happen
   • Actual: What actually happened
   • Status: ✅ Pass / ❌ Fail

2. Test Case 2: Description

   • Expected: What should happen
   • Actual: What actually happened
   • Status: ✅ Pass / ❌ Fail

Test Results

# Include any relevant test output or results

Impact Assessment

Backward Compatibility

• This change maintains backward compatibility
• This change requires migration steps (document below)
• This change introduces breaking changes (document below)

Migration Steps (if applicable)

1. Step 1
2. Step 2
3. Step 3

Breaking Changes (if applicable)

• Change 1: Description and migration path
• Change 2: Description and migration path

Security Considerations

• No security implications
• Credentials handling reviewed
• Input validation implemented
• Error messages don't expose sensitive information
• Secure communication protocols used
• Access controls verified

Performance Impact

• No performance impact expected
• Performance improvements expected
• Potential performance degradation (explain below)

Performance Notes

Describe any performance considerations or measurements.

Dependencies

New Dependencies

• No new dependencies
• New PowerShell modules required
• New external tools required
• Updated minimum system requirements

Dependency Details

List any new or updated dependencies:

• Dependency 1: Version and purpose
• Dependency 2: Version and purpose

Deployment Notes

Pre-deployment Steps

1. Step 1
2. Step 2

Post-deployment Steps

1. Step 1
2. Step 2

Rollback Plan

Describe how to rollback these changes if issues arise.

Screenshots/Examples (if applicable)

Before

Describe or show the behavior before this change.

After

Describe or show the behavior after this change.

# Example usage or output

Code Quality

• Code follows PowerShell best practices
• Functions include proper comment-based help
• Error handling is implemented appropriately
• Code is properly commented
• Variable names are descriptive
• Functions are modular and reusable
• Logging is appropriate and informative

Documentation

• Code changes are documented
• README updated (if needed)
• CONTRIBUTING.md updated (if needed)
• Inline documentation added/updated
• Examples provided for new features

Checklist

Before Submitting

• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published

Testing Verification

• All tests pass
• Code has been tested in multiple environments
• Breaking changes are documented
• Performance impact has been considered

Code Standards

• Code follows the project's style guidelines
• Self-review of the code has been performed
• Code has been checked for security vulnerabilities
• Error handling has been implemented

Additional Notes

Add any additional information that reviewers should be aware of.

Reviewer Instructions

Areas to Focus On

• Focus area 1
• Focus area 2
• Focus area 3

Questions for Reviewers

• Question 1
• Question 2

---

Note to Reviewers: Please ensure all checkboxes are ticked before approving this PR. If any items are not applicable, please mark them as such in the review comments.

[a-ariff]

🚀 Good Progress on CodeQL Fix!

Excellent work on addressing the CodeQL configuration issues! I can see you've taken the right approach by:

✅ Positive Changes Made:

• ✓ Changed matrix.language from ['auto'] to ['python'] - Great fix!
• ✓ Removed deprecated category parameter from Initialize step - Exactly right!
• ✓ PowerShell Lint is passing ✓

❌ Still Needs Attention:

1. CodeQL Check Still Failing (1/2 checks)

   • The python analysis is failing after 36s
   • May need to investigate if there's actual Python code to analyze
   • Consider using javascript or removing CodeQL if this is a PowerShell-only repo

2. PR Documentation Incomplete

   • 74 checklist items still unchecked
   • Should check "Configuration change" since this is a workflow update

📝 Recommendation:

Option A: If this repo has no Python code, change to:

languages: ['javascript']  # for JSON/YAML files

Option B: If purely PowerShell, consider removing CodeQL entirely and rely on PowerShell Lint + security scans from PR #2/#3

Option C: Use auto-detection but without the category parameter:

languages: ['auto']
# Remove category parameter completely

Assigned to myself - Happy to help test the next iteration once you choose an approach. This fix addresses the exact issues I identified in PRs #2 and #3!

[a-ariff]

🛠️ CodeQL Language Mismatch - Quick Fix Needed

Issue: Python analysis failing because this is primarily a PowerShell repository.

Recommended Solutions:

1. Enable autobuild and use languages: ['auto'] for automatic detection
2. Or specify correct language: languages: ['javascript'] for JSON/YAML workflow files
3. Or remove CodeQL entirely if PowerShell Lint + security scans from PRs feat: Add enterprise security workflow for PowerShell and policy scan… #2/feat: add comprehensive supply chain security workflow Add supply-ch… #3 provide sufficient coverage

Current Status: ✅ PowerShell Lint passing | ❌ CodeQL python analysis failing (36s timeout)

Next Steps: Choose language approach above, test, and this should be ready for merge. The core workflow fix (removing deprecated 'category' parameter) is solid!