bug_report.yml 3.2 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374
  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 if possible.
  10. Reports with a reproducible example or detailed information will likely receive fixes faster.
  11. - type: textarea
  12. id: description
  13. attributes:
  14. label: Description
  15. description: |
  16. Describe the problem. Code example can be given here.
  17. placeholder: Bug reports with reproducible code or detailed information will be fixed faster.
  18. validations:
  19. required: true
  20. - type: textarea
  21. id: nim-version
  22. attributes:
  23. label: Nim Version
  24. description: |
  25. Can be obtained from `nim -v` on the command line along with the OS/architecture.
  26. For development versions, make sure to include the commit hash.
  27. validations:
  28. required: true
  29. - type: textarea
  30. id: current-logs
  31. attributes:
  32. label: Current Output
  33. description: Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
  34. placeholder: Bug reports with reproducible code or detailed information will be fixed faster.
  35. render: text
  36. - type: textarea
  37. id: expected-logs
  38. attributes:
  39. label: Expected Output
  40. description: Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
  41. placeholder: Bug reports with reproducible code or detailed information will be fixed faster.
  42. render: text
  43. - type: textarea
  44. id: known-workarounds
  45. attributes:
  46. label: Known Workarounds
  47. description: Provide any known workarounds.
  48. validations:
  49. required: false
  50. - type: textarea
  51. id: extra-info
  52. attributes:
  53. label: Additional Information
  54. description: Any additional relevant information.
  55. validations:
  56. required: false
  57. - type: markdown
  58. attributes:
  59. value: |
  60. - Please check whether the problem still exists in the devel branch, which can be installed via [choosenim](https://github.com/nim-lang/choosenim/), [nightlies](https://github.com/nim-lang/nightlies/), or by [creating a temporary build of the compiler](https://nim-lang.github.io/Nim/intern.html#debugging-the-compiler-building-an-instrumented-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) which should give more context on a compiler crash.
  63. - If it's a regression, you can help us by identifying which version introduced the bug by [bisecting](https://nim-lang.github.io/Nim/intern.html#bisecting-for-regressions) or at least trying known past releases (e.g. `choosenim 2.0.0`).
  64. The Nim repo also supports bisecting in issue comments by adding `!nim c`, `!nim js` etc. before a code block, see [nimrun-action](https://github.com/juancarlospaco/nimrun-action).
  65. - [Please, consider a Donation for the Nim project.](https://nim-lang.org/donate.html)