Feature suggestions can be submitted using the "feature" tag. Prior to submission, please look to see if this has already been suggested or solved; if it has and is not resolved, it would be better to comment on the relevant report.
Within your feature report, try to answer the given prompts - in particular, state the specific feature you want and if possible, please state why you want this added to the program.
Bug reports can be submitted using the "bug" tag. Prior to submission, please look to see if this has already been reported or solved; if it has and is not resolved, it would be better to comment on the relevant report.
Within your bug report, try to answer the given prompts. Be as specific as possible - describe your bug to the best of your ability, how to replicate it, and provide information like screenshots, OS and terminal. It can be very useful to help whoever is dealing with the issue!
-`documentation`: If you note a typo, or want to suggest something to do with the documentation of bottom, use this.
-`question`: If you have a question, and not really a suggestion or request, then use this tag.
-`ci`, `investigative`, `refactoring`: Generally, these are for internal use to track issues in order to manage GitHub Projects, and won't be the appropriate topic for a report.
-`other`: If your suggestion or issue doesn't fit those categories, then use this.
- There are some tests, they're mostly for sanity checks. Please run `cargo test` to ensure you didn't break anything important, unless the change will break the test (in which case please amend the tests).
- I use both [clippy](https://github.com/rust-lang/rust-clippy) and [rustfmt](https://github.com/rust-lang/rustfmt) in development (with some settings, see [clippy.toml](./clippy.toml) and [rustfmt.toml](rustfmt.toml)). Note clippy must pass to for PRs to be accepted.
- Create a personal fork of the process and PR that, as per the [fork and pull method](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models).
- Merge against the `master` branch.
- If you encounter a merge conflict, I expect you to resolve this via rebasing to `master`.
- _Ensure your change builds, runs, and works_. Furthermore, state how you checked this, including what platforms you tested on.
- If your change will result in needing to update documentation, please do so. In particular:
- Does the README need to be updated to accommodate your change?
- Does the help action, `?`, need to be updated to accommodate your change?
- Please ensure that CI passes. If it fails, check to see why it fails! Chances are it's clippy.
- If all looks good, then request someone with write access (so basically me, [@ClementTsang](https://github.com/ClementTsang)) to give your code a review. If it's fine, then I'll merge!
