github-com-docker-mailserver/docker-mailserver
1
0
Fork 0
mirror of https://github.com/docker-mailserver/docker-mailserver.git synced 2024-01-19 02:48:50 +00:00
Code Issues Projects Releases Wiki Activity
docker-mailserver/.github/ISSUE_TEMPLATE/question.yml

31 lines
1,022 B
YAML
Raw Permalink Normal View History

GitHub/CI: issue templates improvements (#3225)
2023-04-06 17:28:33 +00:00
name: Other
ci: `question.yml` - Clarify that the issue tracker is not for personal support (#3498) * ci: Revise `question.yml` to better clarify the issue tracker is not for support queries Users have been making low effort reports (_bypassing the dedicated form_) through this alternative that is intended for addressing other concerns related to the project - not troubleshooting user problems. When a user does not want to put the effort in of a full bug report (_and following our debug docs tips that it refers them to_), they should be using the Github Discussions page which provides the same free-form input, but should not require attention of project devs (contributors / maintainers). --- The markdown rendered field above the "Description" input field didn't seem too relevant for this template. I've opted for a markdown comment (so it won't render if kept) into the input field with hopes that'll be more visible to the readers attention. * chore: Fix typo
2023-08-23 14:56:24 +00:00
description: Miscellaneous questions and reports for the project (not support)
follow-up to #3225 (#3229) Misc spelling fixes and resolved imprecise statements. Shortened the bug report introduction a bit further and added a statement about being precise to all templates.
2023-04-07 09:58:51 +00:00
title: 'other: '
GitHub/CI: issue templates improvements (#3225)
2023-04-06 17:28:33 +00:00
labels:
- meta/help wanted
body:
- type: dropdown
id: subject
attributes:
label: Subject
options:
- I would like to contribute to the project
- I would like to configure a not documented mail server use case
- I would like some feedback concerning a use case
ci: `question.yml` - Clarify that the issue tracker is not for personal support (#3498) * ci: Revise `question.yml` to better clarify the issue tracker is not for support queries Users have been making low effort reports (_bypassing the dedicated form_) through this alternative that is intended for addressing other concerns related to the project - not troubleshooting user problems. When a user does not want to put the effort in of a full bug report (_and following our debug docs tips that it refers them to_), they should be using the Github Discussions page which provides the same free-form input, but should not require attention of project devs (contributors / maintainers). --- The markdown rendered field above the "Description" input field didn't seem too relevant for this template. I've opted for a markdown comment (so it won't render if kept) into the input field with hopes that'll be more visible to the readers attention. * chore: Fix typo
2023-08-23 14:56:24 +00:00
- Something else that requires developers attention
GitHub/CI: issue templates improvements (#3225)
2023-04-06 17:28:33 +00:00
validations:
required: true
- type: textarea
id: description
validations:
required: true
ci: Fix `question.yml` template - `value` should be an attribute (#3502) The recent change to this template was invalid, as `value` should have been nested under the `attributes` object.
2023-08-24 12:29:08 +00:00
attributes:
label: Description
value: |
<!---
Please do not use this form to bypass doing a proper bug report.
The issue tracker is for anything relevant to the project itself, not individual support queries.
If you don't want to fill out a bug report, please ask support questions at our community discussions page: https://github.com/orgs/docker-mailserver/discussions
-->
Reference in a new issue Copy permalink