gentle-ai-issue-creation

To sanitize private data before submitting a GitHub issue, replace sensitive environment details like local paths, hostnames, and tokens with standardized placeholders. This ensures compliance and prevents leaking personal user data during bug reporting or feature request workflows.

Creating a compliant GitHub bug report requires using enforced bug reporting templates and including necessary system information. The workflow mandates pre-submission data masking and adherence to a status-based approval lifecycle to ensure maintainer-ready submissions.

Yes, GitHub issue creation enforces an approval workflow by preventing premature pull request creation through a status:approved gate. This ensures maintainers review and approve the standardized, sanitized issue before any code changes proceed.

GitHub issue submissions are rejected for non-compliance when they bypass mandatory templates, fail to apply privacy sanitization to sensitive environment data, or skip the required status:approved gate enforced by the repository's workflow.

No, you cannot use custom formats for GitHub feature requests. The workflow enforces strict template usage for both bug reports and feature requests to standardize submissions, ensure privacy compliance, and guarantee maintainer-ready documentation.

You need to apply data masking protocols for GitHub issues during the pre-submission phase of bug reporting or feature requests. This process replaces local paths, hostnames, and tokens with standardized placeholders to maintain privacy compliance.