Please make all code scanning alerts visible in pull-requests #140754
Replies: 2 comments
-
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
Beta Was this translation helpful? Give feedback.
-
Thanks for sharing your feedback @praiskup! ✨ |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Bug
Body
The current code scanning toolkit only displays alerts directly in the modified
code (i.e., the code visible in the
Files changed
tab). However, changes inthe pull request can indirectly trigger error reports in other parts of the
codebase, including unchanged sections of the modified file or entirely
different files.
If the code scanning backend identifies "new" issues, the UI should display them
in the PR to ensure users don't overlook them.
An instance of this problem (three new issues being added, only two reported in UI): fedora-copr/vcs-diff-lint#35
Beta Was this translation helpful? Give feedback.
All reactions