github: add spoiler tags to issue template #244
Merged
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
- long logs of output or long configs are hard on the eyes and make it
difficult to read through issues as they just take up so much space
- so it would be better, in my opinion, to hide them by default with
spoiler tags, which can be opened up when further investigation is
warranted
- some issue authors have already used this pattern, this just brings
it to the template itself so everyone (hopefully) starts using it
agilgur5
added
the
scope: github
Repository owner
locked as resolved and limited conversation to collaborators
May 7, 2022
agilgur5
added
the
kind: internal
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
long logs of output or long configs are hard on the eyes and make it
difficult to read through issues as they just take up so much space
spoiler tags, which can be opened up when further investigation is
warranted
some issue authors have already used this pattern, this just brings
it to the template itself so everyone (hopefully) starts using it
Tags
Can see examples of spoiler tag usage in #97, #148, and my own #212 (comment)
Can see examples of very long output logs and/or configs in #72, #85, #87, #194, #213, #217
Review Notes
Been meaning to write this PR for quite a while actually, finally got to it 馃槄