chore: open-PR triage status (do not merge) - #76
Closed
undivisible wants to merge 1 commit into
Closed
Conversation
Contributor
Author
|
Superseded — acting on triage directly (no status PR). |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Read-only triage of open PRs #75 #74 #73 #71 #70 #69 #65 #64 #63.
Classifications and reasons are in
TRIAGE.md. Do not merge this PR; it is a status snapshot.correctfunction for code health insrc/store/lifecycle.rs#75 ⚡ Fix N+1 Query in Evidence Scope Validation #73 ⚡ optimize validate_evidence N+1 query in summaries #71 ⚡ Optimize N+1 Query in Profile Validation During Export #70 🔒 Fix Unparameterized String Interpolation in Embeddings Selection #65 🔒 Fix SQL Injection vulnerability in pragma_table_info #63No listed PRs were merged or closed. twenify was skipped.