create-issue

Converting markdown files into GitHub issues is done by parsing ticket content and metadata, then creating tracked issues with preserved labels and cross-references. The tool resolves file stems or bare numbers to find the correct ticket.

Yes, creating GitHub issues from markdown supports attaching labels, resolving cross-references, and updating parent tickets automatically. It distinguishes between Feature, Work, and Investigation tickets to apply the correct labeling and phase handling.

Yes, the markdown to GitHub issue workflow supports generating and managing workflow phase sub-issues. It parses your ticket files and creates the necessary sub-issues based on the ticket type and workflow phase definitions.

Automating GitHub ticketing from local markdown is best handled by a tool that parses ticket files, applies appropriate labels based on ticket type, and creates issues with cross-references. You can invoke it using bare numbers, full file stems, or .md filenames.

Handling different ticket types when creating GitHub issues is managed by distinguishing between Feature, Work, and Investigation tickets. The tool automatically applies the correct labels and phase handling logic based on the parsed ticket type.