can you add 'affected branches' to the secret scanning alert notices

[JoeNunnelley]

Select Topic Area

Question

Body

On the Secrets and Dependabot tabs in the Security page, it would be helpful if you could add the 'affected branches' information you have in the codeql alerts to those types of alerts as well. Ideally this information would also be gettable from the alerts API. This would allow us to better filter fixes for alerts that are in shipping branches vs those in non-shipping or experimental branches.

[akaday]

Hello Joe,

I completely agree that having the 'affected branches' information available in the Secret and Dependabot alert notices, similar to what is provided in CodeQL alerts, would be incredibly useful. This feature would indeed allow for better filtering and prioritizing fixes, especially when dealing with shipping versus non-shipping or experimental branches.

Additionally, making this information accessible through the alerts API would greatly enhance automation capabilities for managing and addressing these alerts across different branches.

Here's an example of how you might use the affected_branches information in a script:

python
import requests

Replace with your actual GitHub token

GITHUB_TOKEN = 'your_github_token'
REPO_OWNER = 'your_repo_owner'
REPO_NAME = 'your_repo_name'

headers = {
'Authorization': f'token {GITHUB_TOKEN}',
'Accept': 'application/vnd.github.v3+json'
}

Example API endpoint to get alerts (this may vary based on your needs)

api_url = f'https://api.github.com/repos/{REPO_OWNER}/{REPO_NAME}/code-scanning/alerts'

response = requests.get(api_url, headers=headers)

if response.status_code == 200:
alerts = response.json()
for alert in alerts:
print(f"Alert: {alert['rule']['id']}")
print(f"Affected Branches: {alert.get('affected_branches', 'N/A')}")
else:
print(f"Failed to retrieve alerts: {response.status_code}")
Thank you for raising this suggestion. It would be a valuable enhancement for the community, and I hope GitHub considers implementing it.

Best regards

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