import-security-issue

Automating Gmail security report conversion requires scanning your security inbox and proposing imports using this workflow, which drafts tracker issues for triage while keeping content confidential.

Deduplication for security report imports works by cross-referencing inbound Gmail candidates against existing tracker issues, pre-filtering already-resolved threads to reduce noise and prevent duplicate triage entries.

Yes, you need GitHub CLI authentication and Gmail MCP access to create and manage trackers when importing security issues, ensuring the workflow can securely coordinate steps from discovery to classification.

Yes, you can surface canned responses and prior rejections directly on-thread to maintain consistent messaging across reporters when filtering out invalid or already-resolved security reports.

The best way to triage inbound security reports without exposing private content is using a workflow that converts emails into tracker issues with Needs triage status while upholding confidentiality of the original private reports.

Inbound security reports are skipped during tracker import when the workflow deduplicates candidates against existing trackers and pre-filters already-resolved threads to reduce noise in your triage queue.