fix(skill): preserve incident comment content#96
Merged
ysyneu merged 2 commits intoJul 22, 2026
Merged
Conversation
2 tasks
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.
Root cause
Audit run audit-20260722T031714Z-auto found session sess_nnZqgRwBRbo2u7YpCpLDSS constructing an incident comment inside double-quoted Bash. Markdown backticks were evaluated as command substitutions before fduty received the argument, so the API stored altered content. The workflow then reported success without reading the mutation back.
End-state fix
Verification
The repository-cached linter was built with Go 1.24 and cannot analyze this Go 1.25.1 module; the same make target passes with the Go 1.25-built linter shown above.