|
1 | 1 | ## Reporting Issues & Feature Requests |
2 | 2 |
|
3 | | -Found a bug, have a suggestion, or want to propose a new language feature? |
| 3 | +Found a bug, have a suggestion, or want to propose a new language feature? Please [open an issue on GitHub](https://github.com/lambda-discipline/lambda-discipline/issues). |
4 | 4 |
|
5 | | -Please create a work item on GitLab: |
| 5 | +Before opening an issue, please: |
6 | 6 |
|
7 | | -<https://gitlab.com/ninthcircle/lambda-discipline/-/work_items> |
| 7 | +* Search the existing issues to make sure the problem or request has not already been reported. |
| 8 | +* Review related issues for existing discussions, workarounds, or possible solutions. |
| 9 | +* Check the documentation and other relevant project resources where appropriate. |
| 10 | +* Provide enough context for others to understand and reproduce the issue or evaluate the proposal. |
8 | 11 |
|
9 | 12 | When reporting a bug, please include: |
10 | 13 |
|
11 | | -* Your operating system and compiler |
12 | | -* The Lambda Discipline version (or commit hash) |
13 | | -* Steps to reproduce the issue |
14 | | -* The expected and actual behavior |
15 | | -* Any relevant source code or error messages |
| 14 | +* Your operating system and compiler/toolchain. |
| 15 | +* The Lambda Discipline version or commit hash. |
| 16 | +* Clear steps to reproduce the issue. |
| 17 | +* The expected behavior and the actual behavior. |
| 18 | +* A minimal reproducible example, where possible. |
| 19 | +* Relevant source code, error messages, logs, or build output. |
| 20 | +* Any workarounds or possible solutions you have already identified. |
| 21 | + |
| 22 | +For feature requests and language proposals, please explain the motivation, intended behavior, and any relevant use cases or prior discussion. |
16 | 23 |
|
17 | 24 | Feature requests, language proposals, editor integrations, documentation improvements, and build system enhancements are all welcome. |
0 commit comments