create-issue

To create a GitHub issue from a failing GitHub Actions run, provide the run or job URL to automatically extract logs, isolate failed pytest node IDs, and file a deduplicated bug report with proper labels.

Yes, you can automatically extract failed pytest node IDs from CI logs by parsing the provided GitHub Actions job URL, filtering the retrieved logs for error-bearing lines, and summarizing the relevant traceback content.

Yes, the issue creation process checks for duplicate GitHub issues by searching existing open issues before creating a new one, ensuring proper deduplication and linking the appropriate issue with correct attribution.

To attribute a CI regression bug to the right test author in GitHub, the system resolves the triggering PR and identifies the most recent author of the failing test file via GitHub APIs before assigning the issue.

The best way to triage multiple failed jobs in a GitHub Actions run is to supply the run URL, which parses the run_id to identify all failed jobs and supports triaging one job or multiple failed jobs simultaneously.

A limitation when converting GitHub Actions job URLs into bug reports is that the parsing and attribution specifically target NVIDIA/Megatron-LM repositories, requiring valid run_id or job_id extraction to fetch and filter job logs accurately.