open-github-issue

Automating GitHub issue publishing is handled by resolving the target repository, composing language-appropriate issue bodies, and using an authentication fallback. It returns a machine-readable JSON payload detailing the mode, issue URL, and publish errors for downstream workflows.

When GitHub issue authentication is unavailable, the system uses a draft-only fallback after exhausting gh CLI and token-based API attempts. It outputs the rendered issue body within a JSON payload instead of failing, retaining the prepared content.

Localizing GitHub issue formatting is supported by detecting the target repository's language from its README. This allows the system to compose language-appropriate issue headers and formatting for the published proposals.

Publishing GitHub issues does not strictly require the gh CLI, as it uses a deterministic authentication fallback. It attempts gh CLI first, then a token-based API call, and finally a draft-only output if no authentication succeeds.

Resolving the target repository for a GitHub issue is done automatically by extracting details from a specified owner/name or from the current git origin. This removes the need for manual repository configuration in your workflow.

Using a JSON payload when publishing feature proposals provides machine-readable outputs containing the mode, issue URL, rendered body, and publish errors. This structured format enables reliable downstream automation and workflow integration.