Gitly


1 
2 <!--
3 
4 Please title your PR as follows: `module: description` (e.g. `time: fix date format`).
5 Always start with the thing you are fixing, then describe the fix.
6 Don't use past tense (e.g. "fixed foo bar").
7 
8 Explain what your PR does and why.
9 
10 If you are adding a new function, please document it and add tests:
11 
12 ```
13 // foo does foo and bar
14 fn foo() {
15 
16 // file_test.v
17 fn test_foo() {
18     assert foo() == ...
19     ...
20 }
21 ```
22 
23 If you are fixing a bug, please add a test that covers it.
24 
25 Before submitting a PR, please run `v test-all` .
26 See also `TESTS.md`.
27 
28 I try to process PRs as soon as possible. They should be handled within 24 hours.
29 
30 Applying labels to PRs is not needed.
31 
32 Thanks a lot for your contribution!
33 
34 -->
35

1
2	<!--
3
4	Please title your PR as follows: `module: description` (e.g. `time: fix date format`).
5	Always start with the thing you are fixing, then describe the fix.
6	Don't use past tense (e.g. "fixed foo bar").
7
8	Explain what your PR does and why.
9
10	If you are adding a new function, please document it and add tests:
11
12	```
13	// foo does foo and bar
14	fn foo() {
15
16	// file_test.v
17	fn test_foo() {
18	assert foo() == ...
19	...
20	}
21	```
22
23	If you are fixing a bug, please add a test that covers it.
24
25	Before submitting a PR, please run `v test-all` .
26	See also `TESTS.md`.
27
28	I try to process PRs as soon as possible. They should be handled within 24 hours.
29
30	Applying labels to PRs is not needed.
31
32	Thanks a lot for your contribution!
33
34	-->
35