@@ -7,18 +7,18 @@ appreciate any level you're willing to do.
7
7
8
8
Need some new functionality to help? You can let us know by opening an
9
9
[ issue] [ new issue ] . It's helpful to look through [ all issues] [ all issues ] in
10
- case its already being talked about.
10
+ case it's already being talked about.
11
11
12
12
## Bug Reports
13
13
14
14
Please let us know about what problems you run into, whether in behavior or
15
15
ergonomics of API. You can do this by opening an [ issue] [ new issue ] . It's
16
- helpful to look through [ all issues] [ all issues ] in case its already being
16
+ helpful to look through [ all issues] [ all issues ] in case it's already being
17
17
talked about.
18
18
19
19
## Pull Requests
20
20
21
- Looking for an idea? Check our [ issues] [ issues ] . If it's look more open ended,
21
+ Looking for an idea? Check our [ issues] [ issues ] . If the issue looks open ended,
22
22
it is probably best to post on the issue how you are thinking of resolving the
23
23
issue so you can get feedback early in the process. We want you to be
24
24
successful and it can be discouraging to find out a lot of re-work is needed.
@@ -41,15 +41,18 @@ As a heads up, we'll be running your PR through the following gauntlet:
41
41
Not everything can be checked automatically though.
42
42
43
43
We request that the commit history gets cleaned up.
44
+
44
45
We ask that commits are atomic, meaning they are complete and have a single responsibility.
45
- PRs should tell a cohesive story, with test and refactor commits that keep the
46
+ A complete commit should build, pass tests, update documentation and tests, and not have dead code.
47
+
48
+ PRs should tell a cohesive story, with refactor and test commits that keep the
46
49
fix or feature commits simple and clear.
47
50
48
- Specifically, we would encouage
51
+ Specifically, we would encourage
49
52
- File renames be isolated into their own commit
50
- - Add tests in a commit before their feature or fix, showing the current behavior.
53
+ - Add tests in a commit before their feature or fix, showing the current behavior (i.e. they should pass) .
51
54
The diff for the feature/fix commit will then show how the behavior changed,
52
- making it clearer to reviewrs and the community and showing people that the
55
+ making the commit's intent clearer to reviewers and the community, and showing people that the
53
56
test is verifying the expected state.
54
57
- e.g. [ clap #5520 ] ( https://github.com/clap-rs/clap/pull/5520 )
55
58
0 commit comments