create-issue

To create a GitHub issue from a failed GitHub Actions run, share the run or job URL to extract verbatim failure logs, identify root causes, check for duplicate open issues, and assign the ticket to the triggering PR or test-file author.

CI triage for pytest failures works by parsing the GitHub Actions job URL, fetching the relevant error log excerpts, performing root cause analysis, and summarizing the failure with verbatim evidence before linking it to a formatted bug issue.

Yes, you can assign a GitHub issue to the original author by resolving the triggering PR and identifying the last author who modified the failing test file during the CI failure triage process.

Yes, issue creation for CI failures includes duplicate detection by searching for existing open issues that match the failing test, preventing redundant bug reports from being generated for the same GitHub Actions failure.

The best way to format bug reports for GitHub Actions workflow debugging is to extract verbatim error evidence from the logs, link the triggering run and job URLs, and structure the root cause analysis into a standardized GitHub issue.

The issue creation process is specifically designed to format bug reports for the NVIDIA/Megatron-LM repository, applying its root cause extraction and duplicate detection logic to generate correctly formatted GitHub issues for CI failures.