pr-radar-debug

Debug PRRadar by analyzing repository configurations and output artifacts to reproduce issues from the Mac app. Use CLI commands against configured repositories to inspect pipeline outputs, rule evaluation results, and settings directories to identify root causes.

Reproduce PRRadar issues by running CLI commands against your configured repositories to mirror Mac app behavior. Analyze local rule directories, pipeline outputs, and repository settings to replicate the exact environment and trigger the bug.

Yes, you can diagnose PRRadar rule evaluation failures using local repository configurations. Analyze the configured rules, pipeline output artifacts, and settings directories to trace how rules are evaluated and identify where the evaluation logic breaks.

PRRadar pipeline output discrepancies between the Mac app and CLI often stem from mismatched repository configurations or settings. Analyze local rule directories and pipeline outputs to compare environments and locate the configuration differences causing the issue.

Debugging PRRadar with CLI commands is limited to safe, non-destructive guidance using local configurations and publicly available commands. It focuses on analyzing pipeline outputs and settings but does not modify or destructively alter your repository configurations.

You need access to your configured PRRadar repository settings, rule directories, and output artifacts to debug effectively. These local configurations provide the necessary context to reproduce issues, evaluate rules, and verify fixes across your repos.