Remove ML-powered queries #1910
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
adityasharad
reviewed
Oct 2, 2023
Contributor
adityasharad
left a comment
adityasharad
left a comment
There was a problem hiding this comment.
Nice! One question only.
adityasharad
approved these changes
Oct 2, 2023
This was referenced Oct 2, 2023
Contributor
|
Removed the ML-powered queries checks from branch protection. |
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Removes the code to load ML-powered queries since this feature is now fully disabled. For more information, including details on GitHub's investment in AI-powered security technology, see "CodeQL code scanning deprecates ML-powered alerts."
Merge / deployment checklist