Update PR template to mention user-facing changes (#6923)

* Update PR template to mention user-facing changes

* remove checkboxes
This commit is contained in:
Reilly Wood 2022-10-28 09:14:08 -07:00 committed by GitHub
parent 66c2a36123
commit b56e603c58
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -1,21 +1,23 @@
# Description # Description
(description of your pull request here) (Description of your pull request goes here. **Provide examples and/or screenshots** unless the change is trivial)
# Tests # Tests + Formatting
Make sure you've done the following: Make sure you've done the following, if applicable:
- [ ] Add tests that cover your changes, either in the command examples, the crate/tests folder, or in the /tests folder. - Add tests that cover your changes (either in the command examples, the crate/tests folder, or in the /tests folder)
- [ ] Try to think about corner cases and various ways how your changes could break. Cover them with tests. - Try to think about corner cases and various ways how your changes could break. Cover those in the tests
- [ ] If adding tests is not possible, please document in the PR body a minimal example with steps on how to reproduce so one can verify your change works.
Make sure you've run and fixed any issues with these commands: Make sure you've run and fixed any issues with these commands:
- [ ] `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes)
- [ ] `cargo clippy --workspace --features=extra -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - `cargo clippy --workspace --features=extra -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style
- [ ] `cargo test --workspace --features=extra` to check that all the tests pass - `cargo test --workspace --features=extra` to check that all tests pass
# Documentation # User-Facing Changes
- [ ] If your PR touches a user-facing nushell feature then make sure that there is an entry in the documentation (https://github.com/nushell/nushell.github.io) for the feature, and update it if necessary. If you're making changes that will affect the user experience of Nushell (ex: adding/removing a command, changing an input/output type, adding a new flag):
- Get another regular contributor to review the PR before merging
- Make sure that there is an entry in the documentation (https://github.com/nushell/nushell.github.io) for the feature, and update it if necessary