Contributions to Smash Charts are welcome and highly appreciated. I value any feedback, input, or bug reports you might have. Even the smallest contribution counts, and I will always give proper credit and acknowledgement to your contributions.
If you are reporting a bug, please open an issue and include:
- Your operating system name and version.
- Any details about your local setup that might be helpful in troubleshooting.
- Detailed steps to reproduce the bug.
You can never have enough documentation! Please feel free to contribute to any part of the documentation, such as the official docs, docstrings, or even on the web in blog posts, articles, and such.
I am open to ideas and recommendations for enhancements to Smash Charts.
If you are proposing a feature:
- Explain in detail how it would work.
- Keep the scope as narrow as possible, to make it easier to implement.
Look through the GitHub issues for bugs, which will be tagged as bug
.
- Anything tagged with
help wanted
is open to whoever wants to implement it.
Look through the GitHub issues for features, which will be tagged with enhancement
.
- Anything tagged with
help wanted
is open to whoever wants to implement it.
Ready to contribute? Here's how to set up The Super Smash Dashboard for local development.
-
Fork the Smash Charts repository on GitHub.
-
Clone your fork to download a copy of
Smash Charts
locally. -
Use
git
(or similar) to create a branch for local development and make your changes:git switch -c name-of-your-bugfix-or-feature
-
When you're done making changes, check that your changes conform to any code formatting requirements and pass any tests.
-
Commit your changes and open a pull request.
Before you submit a pull request, check that it meets these guidelines:
- The pull request should include additional tests if appropriate.
- If the pull request adds functionality, the docs should be updated.
- The pull request should work for all currently supported operating systems and versions of Python.
Please note that Smash Charts is released with a Code of Conduct. By contributing to this project you agree to abide by its terms.
These contribution guidelines were adapted from the Cookiecutter Repository.