Foundry376/Mailspring
1
1
Fork 0
mirror of https://github.com/Foundry376/Mailspring.git synced 2024-12-26 01:53:13 +08:00
Code Issues Projects Releases Packages Wiki Activity
Mailspring/ISSUE_TEMPLATE.md

38 lines
1.2 KiB
Markdown
Raw Permalink Normal View History

:art: Enhance issue template There were several issues with the last issue template, here are some of them - Instructions to user that should've been comments were not, they were shown as part of the issue - Bullets were used instead of heading, the down side is that they weren't gonna be bullets only. Users were supposed to add paragraphs below them, thus breaking the styling. - There were no separators in place This commit addresses these issues
2016-03-18 10:25:38 +08:00
<!--
gh: Issue template isn't actually displayed as markdown
2016-02-19 02:03:18 +08:00
Thanks for taking the time to file an issue! If you have general question or a problem with your email account, take a quick look at the N1 Knowledge Base to see if you question is addressed there:
:art: Enhance issue template There were several issues with the last issue template, here are some of them - Instructions to user that should've been comments were not, they were shown as part of the issue - Bullets were used instead of heading, the down side is that they weren't gonna be bullets only. Users were supposed to add paragraphs below them, thus breaking the styling. - There were no separators in place This commit addresses these issues
2016-03-18 10:25:38 +08:00
https://support.nylas.com/hc/en-us/sections/203638587-N1_
gh: Initial commit of issue template
2016-02-19 01:55:52 +08:00
Our team tries to respond to all GitHub issues. To make sure your issue is
actionable, try to include the following information:
:art: Enhance issue template There were several issues with the last issue template, here are some of them - Instructions to user that should've been comments were not, they were shown as part of the issue - Bullets were used instead of heading, the down side is that they weren't gonna be bullets only. Users were supposed to add paragraphs below them, thus breaking the styling. - There were no separators in place This commit addresses these issues
2016-03-18 10:25:38 +08:00
-->
gh: Initial commit of issue template
2016-02-19 01:55:52 +08:00
:art: Enhance issue template There were several issues with the last issue template, here are some of them - Instructions to user that should've been comments were not, they were shown as part of the issue - Bullets were used instead of heading, the down side is that they weren't gonna be bullets only. Users were supposed to add paragraphs below them, thus breaking the styling. - There were no separators in place This commit addresses these issues
2016-03-18 10:25:38 +08:00
##### Are there any related issues?
<!-- Try searching for both open and closed issues here: https://github.com/nylas/N1/issues?q=is%3Aissue. Keep in mind that email features are often described differently on different platforms. (Conversations == threads, shortcuts == hotkeys, etc.) -->
...
gh: Issue template isn't actually displayed as markdown
2016-02-19 02:03:18 +08:00
:art: Enhance issue template There were several issues with the last issue template, here are some of them - Instructions to user that should've been comments were not, they were shown as part of the issue - Bullets were used instead of heading, the down side is that they weren't gonna be bullets only. Users were supposed to add paragraphs below them, thus breaking the styling. - There were no separators in place This commit addresses these issues
2016-03-18 10:25:38 +08:00
##### What operating system are you using?
...
gh: Issue template isn't actually displayed as markdown
2016-02-19 02:03:18 +08:00
:art: Enhance issue template There were several issues with the last issue template, here are some of them - Instructions to user that should've been comments were not, they were shown as part of the issue - Bullets were used instead of heading, the down side is that they weren't gonna be bullets only. Users were supposed to add paragraphs below them, thus breaking the styling. - There were no separators in place This commit addresses these issues
2016-03-18 10:25:38 +08:00
##### What version of N1 are you using?
...
gh: Issue template isn't actually displayed as markdown
2016-02-19 02:03:18 +08:00
:art: Enhance issue template There were several issues with the last issue template, here are some of them - Instructions to user that should've been comments were not, they were shown as part of the issue - Bullets were used instead of heading, the down side is that they weren't gonna be bullets only. Users were supposed to add paragraphs below them, thus breaking the styling. - There were no separators in place This commit addresses these issues
2016-03-18 10:25:38 +08:00
--
gh: Initial commit of issue template
2016-02-19 01:55:52 +08:00
fix(issue-template): Update formatting
2016-02-19 03:05:13 +08:00
**Bug?**
Update ISSUE_TEMPLATE.md
2016-07-24 04:03:38 +08:00
##### Do you have any third-party plugins installed? If so, which ones?
:art: Enhance issue template There were several issues with the last issue template, here are some of them - Instructions to user that should've been comments were not, they were shown as part of the issue - Bullets were used instead of heading, the down side is that they weren't gonna be bullets only. Users were supposed to add paragraphs below them, thus breaking the styling. - There were no separators in place This commit addresses these issues
2016-03-18 10:25:38 +08:00
...
gh: Initial commit of issue template
2016-02-19 01:55:52 +08:00
:art: Enhance issue template There were several issues with the last issue template, here are some of them - Instructions to user that should've been comments were not, they were shown as part of the issue - Bullets were used instead of heading, the down side is that they weren't gonna be bullets only. Users were supposed to add paragraphs below them, thus breaking the styling. - There were no separators in place This commit addresses these issues
2016-03-18 10:25:38 +08:00
##### Is the issue related to a specific email provider (Gmail, Exchange, etc.)?
...
gh: Issue template isn't actually displayed as markdown
2016-02-19 02:03:18 +08:00
:art: Enhance issue template There were several issues with the last issue template, here are some of them - Instructions to user that should've been comments were not, they were shown as part of the issue - Bullets were used instead of heading, the down side is that they weren't gonna be bullets only. Users were supposed to add paragraphs below them, thus breaking the styling. - There were no separators in place This commit addresses these issues
2016-03-18 10:25:38 +08:00
##### Is the issue reproducible with a particular attachment, message, signature, etc?
<!-- Try to provide an example as a file attachment or a screenshot. -->
...
gh: Initial commit of issue template
2016-02-19 01:55:52 +08:00
:art: Enhance issue template There were several issues with the last issue template, here are some of them - Instructions to user that should've been comments were not, they were shown as part of the issue - Bullets were used instead of heading, the down side is that they weren't gonna be bullets only. Users were supposed to add paragraphs below them, thus breaking the styling. - There were no separators in place This commit addresses these issues
2016-03-18 10:25:38 +08:00
--
gh: Initial commit of issue template
2016-02-19 01:55:52 +08:00
fix(issue-template): Update formatting
2016-02-19 03:05:13 +08:00
**Feature Request?**
:art: Enhance issue template There were several issues with the last issue template, here are some of them - Instructions to user that should've been comments were not, they were shown as part of the issue - Bullets were used instead of heading, the down side is that they weren't gonna be bullets only. Users were supposed to add paragraphs below them, thus breaking the styling. - There were no separators in place This commit addresses these issues
2016-03-18 10:25:38 +08:00
##### Does this feature exist in another mail client or tool you use?
...
Reference in a new issue Copy permalink