🍪 Contributing

bigtree is a tree implementation package for Python. It integrates with Python lists, dictionaries, and pandas DataFrame.

Thank you for taking the time to contribute. Contributing to this package is an excellent opportunity to dive into tree implementations.

Set Up

First, fork the repository and clone the forked repository.

$ git clone git@github.com:<your-username>/bigtree.git

Next, create a virtual environment and activate it.

$ conda create -n bigtree_venv python=3.10
$ conda activate bigtree_venv

To check if it worked,

$ which pip
/<some directory>/envs/bigtree_venv/bin/pip

From the project folder, install the required python packages locally in editable mode and set up pre-commit checks.

$ python -m pip install -e ".[all]"
$ python -m pip install pre-commit
$ pre-commit install

Developing

After making your changes, create a new branch, add and commit your changed files. In this example, lets assume the changed file is README.md. If there are any pre-commit changes and/or comments, do modify, re-add and re-commit your files.

$ git checkout -b chore/update-readme
$ git add README.md
$ git commit -m "chore: updated README"

Push your changes to your created branch and create a pull request from your fork.

$ git push origin chore/update-readme

Testing and Documentation

If there are changes related to code, please make sure that the unit tests pass and the code coverage is 100%.

$ python -m pip install pytest coverage
$ pytest --cov-report=term-missing --cov-config=pyproject.toml --cov=bigtree

Make sure your add/update the tests and documentations accordingly.

If there are changes to the docstrings and/or sample codes in the docstring, do run the following lines of code to generate the coverage report and test report for docstrings. Refer to the console log for information on the file location of the reports.

$ python -m pip install hatch
$ hatch run docs:coverage
$ hatch run docs:doctest

Convention and Standards

When creating branches, it is recommended to create them in the format type/action. For example,

$ git checkout -b feat/add-this

During pre-commit checks, this project enforces conventional commits when writing commit messages, and checks and formats code using black, flake8, isort, and mypy. - The regex for conventional commits is as such (?s)(build|ci|docs|feat|fix|perf|refactor|style|test|chore|revert|bump)(\(\S+\))?!?:( [^\n\r]+)((\n\n.*)|(\s*))?$.

For testing, this project uses pytest and coverage package for testing of codes, and docstr-coverage and doctest package for testing of docstrings.

Consequent Changes

Please open an issue to discuss important changes before embarking on an implementation.