aget-promote-issue

To promote a private GitHub issue to a public repository safely, the Skill retrieves the source issue, drafts a sanitized version, blocks promotion if private patterns are detected, and requires explicit principal approval before public filing.

Preventing sensitive information leakage when moving GitHub issues public requires enforced content sanitization, private pattern detection blocking, and explicit principal approval during the governed promotion workflow.

Content sanitization during GitHub issue promotion works by detecting private patterns in the source issue, drafting a sanitized promoted version, and blocking the transfer automatically if sensitive information is found.

You can preview a sanitized GitHub issue before filing it publicly by running the process with a dry-run flag, which generates the promotion content without creating the public issue.

When promoting an issue to a public GitHub repository, only safe labels are transferred through label governance, excluding owner and status labels while cross-referencing the private and public issues with a traceability footer.

Issue promotion requires explicit principal approval before creating a public GitHub issue, presenting a promotion preview that must receive a principal GO signal to proceed with the filing.