False Positives for every gem-handled password assignment

[SampsonCrowley]

Select Topic Area

Bug

Body

in the example shown below, passwords are stored in an encrypted_password column and encryption is handled by the extremely common Devise gem.

this is the correct way to assign a password with devise, but Github flags every assignment, without any regards to the very very very common use case where assignment is done directly in an in-memory-only virtual attribute, and it is stored encrypted in a completely different column

I understand it's better to have a false positive than miss it, but there's no way that I'm aware of to make the scanner stop incorrectly flagging lines at least per repo

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

[SampsonCrowley]

also, Why does it have to repeat the same message multiple times for the same line?