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

Hi @mitja-kleider,

That is definitely a frustrating bug. It looks like GitHub's secret scanning regex is being overly aggressive and is triggering on the string literal f"Bearer {..." combined with the word TOKEN in your environment variable key, completely ignoring the fact that it's wrapped in an os.environ call. The fact that it forgets your "false positive" triage state on unchanged code is definitely an issue on GitHub's end regarding how they track triaged alerts for specific lines.

As a temporary workaround until the GitHub team fixes this tracking bug, you could try slightly refactoring the code to break the specific string pattern the scanner is actively looking for.

For example, separating the variable assignment from the dictionary creation usually bypasses the regex:

Python
token = os.environ.get('MY_SECRET_TOKEN')
headers = {"Authorization": f"Bearer {token}"}
Since the word "Bearer" and the word "TOKEN" are no longer on the exact same line within a dictionary declaration, the dumb scanner will likely skip over it and stop spamming you with alerts. Hope this helps save you some time!