@@ -7,18 +7,18 @@ appreciate any level you're willing to do.
77
88Need some new functionality to help? You can let us know by opening an
99[ 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.
1111
1212## Bug Reports
1313
1414Please let us know about what problems you run into, whether in behavior or
1515ergonomics 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
1717talked about.
1818
1919## Pull Requests
2020
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,
2222it is probably best to post on the issue how you are thinking of resolving the
2323issue so you can get feedback early in the process. We want you to be
2424successful 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:
4141Not everything can be checked automatically though.
4242
4343We request that the commit history gets cleaned up.
44+
4445We 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
4649fix or feature commits simple and clear.
4750
4851Specifically, we would encourage
4952- 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) .
5154 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
5356 test is verifying the expected state.
5457 - e.g. [ clap #5520 ] ( https://github.com/clap-rs/clap/pull/5520 )
5558
0 commit comments