aether-issue-pr

Automating GitHub issue and PR creation with repository templates involves guiding user prompts, drafting content per repository format, and submitting via gh CLI after user confirmation. This ensures correct template usage and proper task linkage.

Drafting a GitHub issue before submission requires collecting task details, matching them to repository issue templates, and presenting a draft for user review. This pre-submission step prevents formatting errors and ensures all required template fields are populated correctly.

Yes, you can use gh CLI to open pull requests that follow repository templates by drafting the PR body according to the template structure first. The automation handles template formatting, issue association, and user confirmation before executing the gh command.

GitHub automation workflows handle missing issue numbers and authentication errors by implementing robust pre-checks for issue status and auth state. When network or sandbox limits block submission, the workflow applies safe retries and escalates with detailed error context if needed.

Yes, user confirmation is required before a workflow submits a pull request or issue to GitHub. The automation drafts the content based on repository templates and pauses for explicit approval, ensuring you maintain control over the actual repository changes.