diff options
| author | espr14 <46957311+espr14@users.noreply.github.com> | 2020-03-18 19:27:20 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-03-18 19:27:20 +0300 |
| commit | 4b25d36df6deb13887bcfc5de617f04042abfe2c (patch) | |
| tree | 124cbc4a5adad6187235beb2b737dd30b62d69cf /.github | |
| parent | 7806df7664cffe8d90f648e6a12024389977bbd9 (diff) | |
Removing Slic3r name and links
Diffstat (limited to '.github')
| -rw-r--r-- | .github/CONTRIBUTING.md | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index ecf8a9177..2bc74fd82 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -1,13 +1,13 @@ -Did you encounter an issue with using Slic3r? Fear not! This guide will help you to write a good bug report in just a few, simple steps. +Did you encounter an issue with using PrusaSlicer? Fear not! This guide will help you to write a good bug report in just a few, simple steps. -There is a good chance that the issue, you have encountered, is already reported. Please check the [list of reported issues](https://github.com/alexrj/Slic3r/issues) before creating a new issue report. If you find an existing issue report, feel free to add further information to that report. +There is a good chance that the issue, you have encountered, is already reported. Please check the [list of reported issues](https://github.com/prusa3d/PrusaSlicer/issues) before creating a new issue report. If you find an existing issue report, feel free to add further information to that report. -If possible, please include the following information when [reporting an issue](https://github.com/alexrj/Slic3r/issues/new): -* Slic3r version (See the about dialog for the version number. If running from git, please include the git commit ID from `git rev-parse HEAD` also.) +If possible, please include the following information when [reporting an issue](https://github.com/prusa3d/PrusaSlicer/issues/new): +* PrusaSlicer version (See the about dialog for the version number. If running from git, please include the git commit ID from `git rev-parse HEAD` also.) * Operating system type + version * Steps to reproduce the issue, including: * Command line parameters used, if any - * Slic3r configuration file (Use ``Export Config...`` from the ``File`` menu - please don't export a bundle) + * PrusaSlicer configuration file (Use ``Export Config...`` from the ``File`` menu - please don't export a bundle) * Expected result * Actual result * Any error messages @@ -17,5 +17,5 @@ If possible, please include the following information when [reporting an issue]( Please make sure only to include one issue per report. If you encounter multiple, unrelated issues, please report them as such. -Simon Tatham has written an excellent on article on [How to Report Bugs Effectively](http://www.chiark.greenend.org.uk/~sgtatham/bugs.html) which is well worth reading, although it is not specific to Slic3r. +Simon Tatham has written an excellent on article on [How to Report Bugs Effectively](http://www.chiark.greenend.org.uk/~sgtatham/bugs.html) which is well worth reading, although it is not specific to PrusaSlicer. |