ginee-file-bug

Automate bug report filing on GitHub by drafting an issue from a template, resolving the target repository from local configuration or git remotes, and creating a labeled issue upon approval. The workflow loads a bug-report template, populates it with project context, and self-lints against mandatory checks before publishing.

A bug report template gets populated with project context by loading the file at core/templates/issues/bug-report.md. The workflow extracts repository details from local/framework.config.yaml or git remote get-url origin, then drafts the issue content for human review before submission.

Yes, you can use this workflow without a framework.config.yaml file. The system resolves the target GitHub repository by inspecting git remote get-url origin and stripping the trailing .git suffix if the local configuration file is missing or lacks the github.repo setting.

The best way to ensure a drafted GitHub issue passes mandatory checks is to use the workflow's self-linting step, which validates the bug report against audience guidelines and surfaces suggested restructures before creating the issue via gh issue create, MCP, or HTTPS+token.

Yes, this bug filing workflow requires manual approval before creating a GitHub issue. It surfaces the drafted bug report for human review, and only upon approval does it execute issue creation with the appropriate labels in the target repository.

Limitations of automating bug filing through a GitHub integration workflow include a mandatory human approval gate before issue creation, reliance on resolving the target repository strictly from local/framework.config.yaml or git remotes, and dependency on a specific bug-report template structure for self-linting to pass.