bug_report.yml 3.3 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677
  1. name: "Bug Report"
  2. description: "Create a new bug report. Have you found an unexpected behavior? Use this form."
  3. title: "Think about the title, twice."
  4. labels: ["unconfirmed"]
  5. body:
  6. - type: markdown
  7. attributes:
  8. value: |
  9. - **Please provide a minimal code example that reproduces the Bug!** :bug:
  10. Reports with a reproducible example and descriptive detailed information will likely receive fixes faster.
  11. - type: textarea
  12. id: description
  13. attributes:
  14. label: Description
  15. description: |
  16. Use DETAILED DESCRIPTIVE information about the problem.
  17. Here, you go into more details about your Bug report. This section can be a few paragraphs long.
  18. placeholder: Bug reports with reproducible code and detailed information will be fixed faster.
  19. validations:
  20. required: true
  21. - type: textarea
  22. id: nim-version
  23. attributes:
  24. label: Nim Version
  25. description: Copy and paste the output of `nim -v` on the command line. For development versions, make sure to include the commit hash.
  26. validations:
  27. required: true
  28. - type: textarea
  29. id: current-logs
  30. attributes:
  31. label: Current Output
  32. description: Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
  33. placeholder: Bug reports with reproducible code and detailed information will be fixed faster.
  34. render: text
  35. - type: textarea
  36. id: expected-logs
  37. attributes:
  38. label: Expected Output
  39. description: Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
  40. placeholder: Bug reports with reproducible code and detailed information will be fixed faster.
  41. render: text
  42. - type: textarea
  43. id: possible-solution
  44. attributes:
  45. label: Possible Solution
  46. description: Propose a possible solution.
  47. validations:
  48. required: false
  49. - type: textarea
  50. id: extra-info
  51. attributes:
  52. label: Additional Information
  53. description: Any additional relevant information.
  54. validations:
  55. required: false
  56. - type: markdown
  57. attributes:
  58. value: |
  59. - Thanks for your contributions!, your Bug report will receive feedback from the community soon...
  60. - Please check whether the problem still exists in the devel branch, see [rebuilding the compiler](https://nim-lang.github.io/Nim/intern.html#rebuilding-the-compiler).
  61. - Consider writing a PR targetting devel branch after filing this, see [contributing](https://nim-lang.github.io/Nim/contributing.html).
  62. - If it's a pre-existing compiler bug, see [Debugging the compiler](https://nim-lang.github.io/Nim/intern.html#debugging-the-compiler)
  63. which should give more context on a compiler crash.
  64. - If it's a regression, you can help us by identifying which version introduced the bug,
  65. see [Bisecting for regressions](https://nim-lang.github.io/Nim/intern.html#bisecting-for-regressions),
  66. or at least try known past releases (e.g. `choosenim 2.0.0`). The Nim repo also supports online bisecting
  67. via making a comment, which contains a code block starting by `!nim c`, `!nim js` etc. , see [nimrun-action](https://github.com/juancarlospaco/nimrun-action).
  68. - [Please, consider a Donation for the Nim project.](https://nim-lang.org/donate.html)