team-issue-publish-github

To publish local engineering issue drafts to GitHub Issues, you can use an automated skill that reads drafts from your local directory and creates corresponding issues on GitHub. This approach handles dependencies and ensures consistent issue tracking without manual data entry.

Yes, a GITHUB_TOKEN is required for authentication to publish issues from local drafts. The token allows the script to securely access your GitHub repository and create issues, apply labels, and assign milestones on your behalf.

Dependency management when publishing GitHub Issues works by following 'Blocked by' relationships defined in your local drafts. The publishing process respects these dependencies, ensuring that linked issues are correctly associated in GitHub for accurate project tracking.

Yes, you can configure custom labels, milestones, and assignees when publishing issues to GitHub. The publishing process supports these custom configurations to ensure detailed issue management directly from your local engineering drafts.

The best way to bulk publish issue drafts for team tracking is to automate the publication from a standardized local directory. Running a dedicated script pushes all drafts under your active team folder to GitHub Issues, streamlining collaboration and reducing manual effort.

Your local issue drafts may not show up in GitHub Issues if they are not placed in the correct directory or if the GITHUB_TOKEN lacks sufficient permissions. Ensure your drafts are correctly formatted and located in the expected team specification folder.