Labels for triaging draft security advisories

[divergentdave]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Other

Discussion Details

I have been receiving a lot of security advisories on a repository I maintain. To aid in triaging these reports, I would like to be able to assign labels to the draft reports, similar to how I can add labels to issues.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[kit1211]

Hi @divergentdave

Labeling draft security advisories for triage is a reasonable request. Today GitHub Security Advisories draft reports do not support custom labels like Issues do.

Current workarounds:

1. Use draft advisory title prefix convention: [Triage], [Accepted], [Duplicate], [Wontfix]

2. Track triage state in a linked Issue using labels. Link advisory to issue via reference in advisory description.

3. Use GitHub Projects board with custom fields for advisory URL and status column.

4. For repositories with high advisory volume, maintain SECURITY_TRIAGE.md with table of GHSA ids and status.

5. API automation: list repository security advisories via GraphQL, sync status to Project v2 custom field via Actions scheduled workflow.

Product feedback to add here: parity between Issue labels and Draft Security Advisory metadata fields including assignee and labels.

Your maintainer workflow pain is valid. Upvote if a linked feature request exists.