Include part of the guide body that has unexpected formatting in the logged message #376
+2
−2
Conversation
This file contains 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
yrodiere
approved these changes
Nov 29, 2024
marko-bekhta
force-pushed
the
test/log-part-of-the-file-with-unexpected-formatting
branch
from
2f18b3a
to
71c10b6
Compare
marko-bekhta
force-pushed
the
test/log-part-of-the-file-with-unexpected-formatting
branch
from
71c10b6
to
209be99
Compare
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.
Not sure if that's worth it or not (it'll log up to 10k chars)... but I noticed this again when looking at the recent staging logs: #319 (comment)
But looking at the files it points to, those seem fine and running the app locally does not produce the warning ... so I wonder what's the content of those files if it says they aren't what we expect ...