Skip to content

Conversation

@github-actions
Copy link
Contributor

Summary

Enhanced debug logging in 5 important Go files to improve troubleshooting and development workflow visibility.

Files Modified

  1. pkg/workflow/safe_outputs_config_generation.go (34KB)

    • Added logging for empty configuration detection
    • Added logging when processing safe job configurations
    • Added logging for final config generation with tool count
  2. pkg/workflow/compiler_yaml_main_job.go (28KB)

    • Added logging for cache/cache-memory/repo-memory step generation
    • Added logging before engine execution and agent completion tracking
  3. pkg/cli/audit_report_render.go (17KB)

    • Added logging for key findings, recommendations, failure analysis
    • Added logging for jobs table rendering with counts
  4. pkg/cli/update_workflows.go (16KB)

    • Added logging for workflow update start/success/failure
    • Added logging for workflow discovery process
  5. pkg/parser/include_processor.go (9KB)

    • Added new logger declaration with proper naming convention
    • Updated existing log statements to use dedicated logger
    • Added logging for file reading, validation, and processing

Logging Guidelines Followed

All changes adhere to the project's logging guidelines from AGENTS.md:

  • ✅ Logger naming uses pkg:filename pattern
  • ✅ Log messages are meaningful and helpful for debugging
  • ✅ No side effects in logger arguments
  • ✅ Logs function entry with relevant parameters
  • ✅ Logs important state changes and control flow decisions
  • ✅ No duplication with user-facing console messages

Validation

  • Build: Successful compilation with make build
  • Tests: Validated via workflow compilation
  • Debug Logs: Confirmed visible during DEBUG=* ./gh-aw compile dev

Testing

To see the new logging in action:

DEBUG=* ./gh-aw compile dev

This will show detailed debug output from all enhanced files during workflow compilation.

🤖 Generated with [Claude Code]((claude.com/redacted)

AI generated by Go Logger Enhancement

  • expires on Feb 12, 2026, 7:48 AM UTC

Enhanced debug logging in workflow compilation, audit reporting, workflow
updates, and include processing to improve visibility during development
and troubleshooting.

Files modified:
- pkg/workflow/safe_outputs_config_generation.go: Added logging for config generation steps
- pkg/workflow/compiler_yaml_main_job.go: Added logging for cache and engine steps
- pkg/cli/audit_report_render.go: Added logging for report rendering sections
- pkg/cli/update_workflows.go: Added logging for workflow update operations
- pkg/parser/include_processor.go: Added dedicated logger and enhanced logging

All changes follow project logging guidelines with meaningful messages,
proper logger naming (pkg:filename), and no side effects in log arguments.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@github-actions
Copy link
Contributor Author

🔍 PR Triage Results

Category: bug | Risk: high | Priority: 58/100

Scores Breakdown

  • Impact: 40/50 - Bug fix affecting core workflow compilation files - high user impact
  • Urgency: 8/30 - Recent PR (4.7 hours old), high risk increases urgency
  • Quality: 10/20 - Baseline quality, pending CI validation

📋 Recommended Action: batch_review

Rationale: High-risk bug fix in core workflow files (pkg/workflow/*) requires careful review despite medium priority score. Changes touch compilation logic which is critical to system functionality.

Review Focus:

  • Verify debug logging doesn't expose sensitive information
  • Check performance impact of additional logging
  • Ensure logging is conditional (debug mode only)
  • Validate changes in core compilation files

Triaged by PR Triage Agent on 2026-02-10

AI generated by PR Triage Agent

@pelikhan pelikhan merged commit 78b0516 into main Feb 10, 2026
48 checks passed
@pelikhan pelikhan deleted the main-c9de904847c58095 branch February 10, 2026 15:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant