From 2dc4681d913f816c4232673c6dcd7891ba17525f Mon Sep 17 00:00:00 2001 From: Nino van Hooff Date: Fri, 6 Dec 2019 14:29:05 +0100 Subject: Remove some mid-sentence newlines from issue templates Newlines are tragically not ignored by Github when rendering issue\ templates, it seems --- .github/ISSUE_TEMPLATE.md | 15 +++++---------- .github/ISSUE_TEMPLATE/bug-report.md | 15 +++++---------- 2 files changed, 10 insertions(+), 20 deletions(-) (limited to '.github') diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md index 10ebdd761c..02fc0f1a65 100644 --- a/.github/ISSUE_TEMPLATE.md +++ b/.github/ISSUE_TEMPLATE.md @@ -32,10 +32,8 @@ In the case of visual glitches/issues, also include information about your graph 2. Something you did next. **Screenshot(s)** -Adding screenshot(s) is a very good idea to identify what exactly the problem is. We get lots of bug reports and a -screenshot is also a great help to tell them apart without downloading and opening a project file. Feel -free to add text either inside or below the screenshots. Before (earlier, working version of Cura) / After -(Problematic version of Cura) screenshots might work well, too. +Adding screenshot(s) is a very good idea to identify what exactly the problem is. We get lots of bug reports and a screenshot is also a great help to tell them apart without downloading and opening a project file. +Feel free to add text either inside or below the screenshots. Before (earlier, working version of Cura) / After (Problematic version of Cura) screenshots might work well, too. **Actual results** (What happens after the above steps have been followed.) @@ -45,15 +43,12 @@ free to add text either inside or below the screenshots. Before (earlier, workin **Project file** Provide a project which clearly shows the bug. -Rather than providing a model file, provide a project (.3mf or .curaproject) file. This will include all the settings -you used, which is crucial to reproducing your problem. +Rather than providing a model file, provide a project (.3mf or .curaproject) file. This will include all the settings you used, which is crucial to reproducing your problem. To upload a project, try changing the extension to e.g. bug_example.3mf.zip so that GitHub accepts uploading the file. -If the file is too big, we recommend http://wetransfer.com, but other file hosts like Google Drive or Dropbox work -well too. Please make sure the file is publicly available ie. "shared with everyone" +If the file is too big, we recommend http://wetransfer.com, but other file hosts like Google Drive or Dropbox work well too. Please make sure the file is publicly available ie. "shared with everyone" **Log file** -It is important to provide a log file. It might provide us info about why a certain material was selected, or is not -compatible, for example. +It is important to provide a log file. It might provide us info about why a certain material was selected, or is not compatible, for example. Information about how to find the log file can be found at https://github.com/Ultimaker/Cura#logging-issues **Additional information** diff --git a/.github/ISSUE_TEMPLATE/bug-report.md b/.github/ISSUE_TEMPLATE/bug-report.md index 10ebdd761c..02fc0f1a65 100644 --- a/.github/ISSUE_TEMPLATE/bug-report.md +++ b/.github/ISSUE_TEMPLATE/bug-report.md @@ -32,10 +32,8 @@ In the case of visual glitches/issues, also include information about your graph 2. Something you did next. **Screenshot(s)** -Adding screenshot(s) is a very good idea to identify what exactly the problem is. We get lots of bug reports and a -screenshot is also a great help to tell them apart without downloading and opening a project file. Feel -free to add text either inside or below the screenshots. Before (earlier, working version of Cura) / After -(Problematic version of Cura) screenshots might work well, too. +Adding screenshot(s) is a very good idea to identify what exactly the problem is. We get lots of bug reports and a screenshot is also a great help to tell them apart without downloading and opening a project file. +Feel free to add text either inside or below the screenshots. Before (earlier, working version of Cura) / After (Problematic version of Cura) screenshots might work well, too. **Actual results** (What happens after the above steps have been followed.) @@ -45,15 +43,12 @@ free to add text either inside or below the screenshots. Before (earlier, workin **Project file** Provide a project which clearly shows the bug. -Rather than providing a model file, provide a project (.3mf or .curaproject) file. This will include all the settings -you used, which is crucial to reproducing your problem. +Rather than providing a model file, provide a project (.3mf or .curaproject) file. This will include all the settings you used, which is crucial to reproducing your problem. To upload a project, try changing the extension to e.g. bug_example.3mf.zip so that GitHub accepts uploading the file. -If the file is too big, we recommend http://wetransfer.com, but other file hosts like Google Drive or Dropbox work -well too. Please make sure the file is publicly available ie. "shared with everyone" +If the file is too big, we recommend http://wetransfer.com, but other file hosts like Google Drive or Dropbox work well too. Please make sure the file is publicly available ie. "shared with everyone" **Log file** -It is important to provide a log file. It might provide us info about why a certain material was selected, or is not -compatible, for example. +It is important to provide a log file. It might provide us info about why a certain material was selected, or is not compatible, for example. Information about how to find the log file can be found at https://github.com/Ultimaker/Cura#logging-issues **Additional information** -- cgit v1.2.3