Repository navigation
docs(graph): drop a wrong finding id from the edge-scope comment - #179
Merged
Merged
Conversation
The comment labelled the target-side layer predicate F105, but F105 is a different audit item (layer in episode_get, raw connections, cluster mixing). A reader searching that id would land on the wrong finding.
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
 |
github-actions
Bot
added
the
documentation
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
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.
The comment introduced by #177 labelled the target-side layer predicate
F105, but F105 is a different audit item (layer inepisode_get, raw connections, cluster mixing). A reader searching that id lands on the wrong finding. Two lines, comment only.