Hexdropper is an open source project. Contributions to this project are always welcome and appreciated!
The best and easiest way to contribute to this project is by submitting an issue or pull request on our GitHub repo.
When submitting an issue or pull request, please be as detailed and specific as possible to ensure that other contributors fully understand the issues you are reporting or any proposed changes you are making. It is always better to err on the side of more explanations than less! :)
If you are reporting a bug, please submit an issue and include the following information:
- Your operating system name and version.
- Any details about your local setup that might be helpful in troubleshooting.
- Detailed steps to reproduce the bug.
Look through the project's issues page for bugs. Issues tagged with bug
, enhancement
, or help wanted
are open to contributors who would like to implement it.
You can never have enough documentation! Please feel free to contribute to any part of the documentation, such as the official docs, docstrings, examples, or even on the web in blog posts, articles, and such.
If you are proposing a new feature:
- Explain in detail how it would work and try to be as specific as possible.
- Keep the scope as narrow as possible to make it easier to implement.
- Remember that this is a volunteer-driven project, and that contributions are welcome :)
If you would like to submit general feedback, or would like to contribute in ways that are not outlined above (e.g., fixing typo/spelling mistake, factual error), please submit an issue with your proposed suggestions or changes.
Ready to contribute? Here's how to set up hexdropper
for local development.
-
Fork the project repository and download a copy of
hexdropper
locally. -
Install
hexdropper
usingpoetry
:$ poetry install
If you are unfamiliar with poetry
, please check out this link
-
Use
git
(or similar) to create a branch for local development and make your changes:$ git checkout -b name-of-your-bugfix-or-feature
-
When you're done making changes, check that your changes conform to any code formatting requirements and pass all tests.
-
Commit your changes and open a pull request.
Before you submit a pull request, check that it meets these guidelines:
- Whenever possible, the pull request should always include additional tests.
- If the pull request adds functionality, any relevant docs should be updated.
- The pull request should work for all currently supported operating systems and versions of Python.
Please note that the hexdropper
project is released with a Code of Conduct. By contributing to this project you agree to abide by its terms.