🚨 Dismissal Comments Missing for Dependabot Alerts – Possibly Widespread

[SAIKARTHIKGOTURI]

Select Topic Area

Bug

Body

Hi all,

I'm noticing a bug related to Dependabot security alert dismissals where the dismissal comment isn't being saved or shown in the UI, and the dismissed_comment field is also coming through as null in the webhook/API payload.

🔎 Issue Summary
When dismissing a Dependabot alert with a dismissal_reason and a dismissal_comment, the reason is captured properly, but the comment is lost.

✅ Expected Behavior
The comment should be visible in the GitHub UI alongside the dismissed alert.

The webhook payload (dependabot_alert.dismissed) should include the dismissed_comment field with the submitted text.

❌ Actual Behavior
The dismissal_reason is recorded correctly.

The dismissal_comment is missing in both the UI and the webhook payload (null).

📈 Observations
Initially seen in a single repository.

Now appearing across multiple repositories, suggesting the issue may be widespread.

Breaks workflows that rely on dismissal comments for auditing or automation.

🧪 Reproduction Steps
Go to a repository with an open Dependabot alert.

Dismiss the alert with a reason (e.g., “not vulnerable”) and add a comment.

Observe that the comment is not saved or visible in the UI.

If listening to webhooks, inspect the dependabot_alert.dismissed payload — the dismissed_comment field will be null.

🛠️ Impact
This causes problems for any process that depends on having a reason and a comment for alert dismissals (e.g., for compliance, review, or automated workflows).

📩 Request
Has anyone else run into this issue recently? Would be helpful to know if this is platform-wide or isolated to certain environments. If there are any workarounds or GitHub updates available, please share!

Thanks!

[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. ⭐