Contributing#

Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given.

You can contribute in many ways:

Types of Contributions#

Report Bugs#

Report bugs at balouf/package-helper-3#issues

If you are reporting a bug, please 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.

Fix Bugs#

Look through the GitHub issues for bugs. Anything tagged with “bug” and “help wanted” is open to whoever wants to implement a fix for it.

Implement Features#

Look through the GitHub issues for features. Anything tagged with “enhancement” and “help wanted” is open to whoever wants to implement it.

Write Documentation#

Package Helper 3 could always use more documentation, whether as part of the official docs, in docstrings, or even on the web in blog posts, articles, and such.

Submit Feedback#

The best way to send feedback is to file an issue at balouf/package-helper-3#issues.

If you are proposing a new feature:

  • Explain in detail how it would work.

  • 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 :)

Get Started!#

Ready to contribute? Here’s how to set up package-helper-3 for local development. Please note this documentation assumes you already have poetry and Git installed and ready to go.

  1. Fork the package-helper-3 repo on GitHub.

  2. Clone your fork locally:

    cd <directory_in_which_repo_should_be_created>
git clone git@github.com:YOUR_NAME/package-helper-3.git

  3. Now we need to install the environment. Navigate into the directory:

    cd package-helper-3

    Install and activate the environment with:

    poetry install

  4. Create a branch for local development:

    git checkout -b name-of-your-bugfix-or-feature

    Now you can make your changes locally.

  5. Don’t forget to add test cases for your added functionality as doctests or in the tests directory.

  6. When you’re done making changes, check that your changes pass the tests:

    pytest

  7. Before raising a pull request you should also run tox. This will run the tests across different versions of Python:

    tox
    This requires you to have multiple versions of python installed.

    This step is also triggered in the CI/CD pipeline, so you could also choose to skip this step locally.

  8. Commit your changes and push your branch to GitHub:

    git add .
git commit -m "Your detailed description of your changes."
git push origin name-of-your-bugfix-or-feature

  9. Submit a pull request through the GitHub website.

Pull Request Guidelines#

Before you submit a pull request, check that it meets these guidelines:

  1. The pull request should include tests.

  2. If the pull request adds functionality, the docs should be updated. Put your new functionality into a function with a docstring, and add the feature to the list in README.md.

  3. The pull request should work for the last three stable Python release, e.g. 3.9, 3.10, and 3.11 if Python 3.11 is the latest stable version.