Test: malformed .hacktron/config.yaml fails open silently#39
Open
alan-hacktron wants to merge 1 commit into
Open
Test: malformed .hacktron/config.yaml fails open silently#39alan-hacktron wants to merge 1 commit into
alan-hacktron wants to merge 1 commit into
Conversation
Owner
Author
|
Demonstrating the malformed-config gap: .hacktron/config.yaml on main currently has invalid YAML (unclosed bracket in skip.branches). Backend logs a warning server side, but this PR gets no check run annotation and no comment about it. The scan above proceeds as if there were no config at all. This is the fail open behavior flagged in the deploy risk review. |
This was referenced Jul 3, 2026
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
1 participant
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.
This PR targets main while .hacktron/config.yaml on main has invalid YAML (unclosed bracket in skip.branches). Expect: config is ignored (logged as a warning server side only), scan proceeds normally, and no check run or comment tells the author their config was broken.