1 | <!-- |
2 | |
3 | Please title your PR as follows: `module: description` (e.g. `time: fix date format`). |
4 | Always start with the thing you are fixing, then describe the fix. |
5 | Don't use past tense (e.g. "fixed foo bar"). |
6 | |
7 | Explain what your PR does and why. |
8 | |
9 | If you are adding a new function, please document it and add tests: |
10 | |
11 | ``` |
12 | // foo does foo and bar |
13 | fn foo() { |
14 | |
15 | // file_test.v |
16 | fn test_foo() { |
17 | assert foo() == ... |
18 | ... |
19 | } |
20 | ``` |
21 | |
22 | If you are fixing a bug, please add a test that covers it. |
23 | |
24 | Before submitting a PR, please run `v test-all` . |
25 | See also `TESTS.md`. |
26 | |
27 | I try to process PRs as soon as possible. They should be handled within 24 hours. |
28 | |
29 | Applying labels to PRs is not needed. |
30 | |
31 | Thanks a lot for your contribution! |
32 | |
33 | --> |
34 | |
35 | <!-- |
36 | |
37 | ATTENTION! ⚠️ |
38 | |
39 | The below commands will be replaced with Copilot AI generated PR description. |
40 | This description will be automatically updated to describe the latest commit of this PR. |
41 | If you decided to remove them - please, provide a detailed description of your changes. |
42 | |
43 | --> |
44 | |
45 | copilot:summary |
46 | |
47 | copilot:walkthrough |