fix: use @ before path in -vv startup pointer message - #3543
Merged
Conversation
Matches the codebase convention for associating an entity with a location, and the wording PR #3521 already applied to the -vv end-of-run block.
worktrunk-bot
approved these changes
Jul 22, 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
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.
The `-vv` startup pointer (`announce_trace_destination` in `src/logging.rs`) printed "Verbose logging to <dir>/", using "to" before the path. The codebase convention (see the `writing-user-outputs` skill) is `@` before paths in user-facing output — #3521 already applied this to the `-vv` end-of-run block but left this start-of-run pointer as the one remaining inconsistency.
Changes "Verbose logging to <dir>/" to "Verbose logging @ <dir>/" and updates the matching test assertions/doc comment in `tests/integration_tests/diagnostic.rs`. The historical wording quoted in `CHANGELOG.md` is left as-is since it documents a past release.