chore: Update bug_report.yaml to reassure our policy on questions #9572
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
github-actions
bot
added
the
:type/dev
cnrpman
changed the title
Bad3r
approved these changes
Jun 3, 2023
|
|
||
| Please make sure to provide a descriptive, deterministic, and reproducible report. It saves time for both the developers and users who are looking for solutions. Providing as much information as possible, including screenshots and logs, is highly appreciated. This will help us to better understand the issue and respond more effectively. | ||
|
|
||
| Please DO NOT use this template to ask questions. There are other appropriate channels to ask questions. This template is strictly for reporting bugs. |
There was a problem hiding this comment.
Non-blocking: **Bold** formatting could be used instead of capitalization or in combination with it to emphasize parts of the text.
Thank you for asking for input :D
cnrpman
force-pushed
the
chore/bug-report-no-question
branch
from
833fc77
to
9d498e4
Compare
Bad3r
added a commit
to Bad3r/Logseq
that referenced
this pull request
Jun 4, 2023
* Remove deprecated :editor/command-trigger option This option has been deprecated for a couple months * enhance: auto pan * enhance: naming * fix: e2e tests * enhance: support whiteboard translations * fix: add whitespace * Update valid dicts lint and delete an unused key * enhance: add tooltip hint for prefered-file-paste (logseq#9564) * enhance: add tooltip hint for prefered-file-paste * Revert dict changes This reverts commit 65cf1ee. * chore: Update bug_report.yaml to reassure no question (logseq#9572) --------- Co-authored-by: Gabriel Horner <gabriel@logseq.com> Co-authored-by: Konstantinos Kaloutas <konstantinos@logseq.com> Co-authored-by: Junyi Du <junyidu.cn@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.
Some users may overlook the "bug only" policy of the issue section. This results in the creation of multiple tickets that lack of description, which can clutter the issues section and divert our attention from addressing legitimate bugs and prioritizing developments.
(Not creating the links toward tickets on purpose. And it's not a single case.)
Example: 9569 9570
Of course, in practice, we should still keep gentle towards the question tickets.