demo(01-safe-typo-fix): 01 — Safe typo / wording fix (clean)#150
Open
demo(01-safe-typo-fix): 01 — Safe typo / wording fix (clean)#150
Conversation
See scenarios/01-safe-typo-fix/README.md for the expected verdict.
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.
01 — Safe typo / wording fix (clean)
Expected verdict: ✅ Clean — GauntletCI should produce no findings.
What changed
A cosmetic fix in
src/OrderService/Logging/RequestLogger.cs:"HTTP"to"Http"in the structured log format string.cid=field label tocorrelationId=for readability.No behavioural change. No new dependencies. No public-surface change.
This is the kind of PR you want your CI to wave through.
Why this scenario exists
GauntletCI must be quiet on safe changes. If this PR comes back with any
finding, the noise/precision balance is off.