chore: use markdown to display github comments truncation header #4885
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
benoittoulme
requested review from
GenPage,
lukemassa and
X-Guardian
and removed request for
a team
chenrui333
changed the title
1 task
|
@chenrui333 as you reviewed this PR, you may be interested in the follow-up PR #4980 |
a1k0u
pushed a commit
to a1k0u/atlantis
that referenced
this pull request
Nov 1, 2024
…atlantis#4885) Co-authored-by: Rui Chen <rui@chenrui.dev> Signed-off-by: a1k0u <alko7enko@gmail.com>
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.
what
This is a follow-up to #3905
I noticed the truncation header is not formatted properly, and looks kind of ugly:
I propose to use github markdown notation instead to format the header as a warning message:
why
tests
references
#3905