Skip to content
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 12 additions & 4 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,17 +37,25 @@ Before submitting a PR make sure to run:
- for formatting

```shell
cargo fmt --all
cargo fmt --all -- --check
```

- the clippy lints
- the clippy lints (with warnings treated as errors)

```shell
cargo clippy
cargo clippy --all-targets --all -- -D warnings
```

- the test suite

```shell
cargo test
cargo test --all
```

- the lockfile check

```shell
cargo check --locked --all-targets --all
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure how many times that is actually relevant? Have you run into that failing?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hi @sholderbach thanks for the feedback! I think i was a bit thrown off by the github actions CI calling this command, as parity with CI was the priority for this PR. It seems like clippy covers this behavior (checking that Cargo.lock matches Cargo.toml) and so i've edited the instructions with some consolidated commands and clarifying notes. While I believe this should cover things as far as matching CI, I wonder if some of the steps in the gh workflow can be consolidated?

```

Note: CI runs these checks across multiple feature combinations (`bashisms`, `sqlite`, `external_printer`, etc.), so you may want to test with the features relevant to your changes using the `--features` flag.