mirror of
https://github.com/ClementTsang/bottom.git
synced 2026-10-10 03:01:29 +00:00
Making it so that new features have to go through a feature request first. I'm somewhat not a fan of getting random feature PRs out of the blue - I feel bad saying no too. I would rather be upfront and say that look, if you want a feature, make a feature request and discuss it first before you waste time/tokens/whatever on it.
2.1 KiB
2.1 KiB
Description
A description of the change, what it does, and why it was made. If relevant (e.g. UI changes), please also provide screenshots or recordings:
Issue
If applicable, what issue does this address? Note that if this is for a new feature, please create an issue first and let it be discussed first. PRs that do not follow this may be closed.
Closes: #
Testing
If relevant, please state how this was tested (including steps):
If this change affects the program, please also indicate which platforms were tested:
- Windows
- macOS (specify version below)
- Linux (specify distro below)
- Other (specify below)
Checklist
Ensure all of these are met:
- If this pull request adds or changes a dependency, please justify this in the description
- If this is a code change, areas your change affects have been linted using (
cargo fmt) - If this is a code change, your changes pass
cargo clippy --all -- -D warnings - If this is a code change, new tests were added if relevant
- If this is a code change, your changes pass
cargo test - The change has been verified to work (see the Testing section) and doesn't unexpectedly break anything else
- Documentation has been updated if needed (
README.md, help menu, docs, configs, etc.) - There are no merge conflicts
- You have personally reviewed your changes already before creating the PR
- The pull request passes the provided CI pipeline
- If the changes were generated with AI tools:
- Ensure it fully follows the AI policy.
- Specify how it was used in the "Other" section.
- Ensure that you, as a human, have personally reviewed the change
Other
Anything else that maintainers should know about this PR: