Auto-Close on Removal

[snair19-wowcorp]

Select Topic Area

General

Body

Hi GitHub Team and community,

We have the following scenario: A developer accidentally commits a secret. Upon detection, they move the secret to a Vault and remove the plaintext string from the code in a subsequent commit.

Current behaviour and feature request: GitHub continue to report these as "Open" alerts even after they are no longer present in the current commit? While we understand the secret remains in the Git history, we would like a setting/feature within GHAS to auto-close alerts based on this criteria. This would minimise dashboard noise and expedite the secret remediation process.

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

[itxashancode]

I've run into this too. GHAS secret scanning alerts do auto-close when the secret is removed from the default branch's latest commit, but the setting must be enabled.

Check your repository settings:
Settings > Code security and analysis > Secret scanning > enable "Dismiss alerts when the secret is no longer present".

This only works on the default branch (usually main/master). If you remove the secret on a feature branch or in a PR, the alert stays open until that fix is merged to default. The secret.