Contributing to Ibis
Set up a development environment
Create a fork of the Ibis repository, and clone it.
git clone https://github.com/<your-github-username>/ibis
Download and install Miniconda
Create a Conda environment suitable for ibis development:
cd ibis conda env create
Activate the environment
conda activate ibis-dev
Install your local copy of Ibis into the Conda environment. In the root of the project run:
pip install -e .
Find an issue to work on
If you are working with Ibis, and find a bug, or you are reading the documentation and see something wrong, or that could be clearer, you can work on that.
But sometimes, you may want to contribute to Ibis, but you don't have anything in mind. In that case, you can check the GitHub issue tracker for Ibis, and look for issues with the label good first issue. Feel free to also help with other issues that don't have the label, but they may be more challenging, and require knowledge of Ibis internals.
Once you found an issue you want to work on, write a comment with the text
/take, and GitHub will
assign the issue to yourself. This way, nobody else will work on it at the same time. If you find an
issue that someone else is assigned to, please contact the assignee to know if they are still working
Working with backends
Ibis comes with several backends. If you want to work with a specific backend, you will have to install
the dependencies for the backend with
conda install -n ibis-dev -c conda-forge --file="ci/deps/<backend>.yml".
If you don't have a database for the backend you want to work on, you can check the configuration of the
continuos integration, where docker images are used for different backend. This is defined in
Run the test suite
To run Ibis tests use the next command:
PYTEST_BACKENDS="sqlite pandas" python -m pytest ibis/tests
You can change
sqlite pandas by the backend or backends (space separated) that
you want to test.
Style and formatting
We use flake8,
isort to ensure our code
is formatted and linted properly. If you have properly set up your development
environment by running
make develop, the pre-commit hooks should check
that your proposed changes continue to conform to our style guide.
We use numpydoc as our standard format for docstrings.
We aim to make our individual commits small and tightly focused on the feature they are implementing. If you find yourself making functional changes to different areas of the codebase, we prefer you break up your changes into separate Pull Requests. In general, a philosophy of one Github Issue per Pull Request is a good rule of thumb, though that isn't always possible.
We avoid merge commits (and in fact they are disabled in the Github repository)
so you may be asked to rebase your changes on top of the latest commits to
master if there have been changes since you last updated a Pull Request.
Rebasing your changes is usually as simple as running
git pull upstream master --rebase and then force-pushing to your branch:
git push origin <branch-name> -f.
Well-structed commit messages allow us to generate comprehensive release notes
and make it very easy to understand what a commit/PR contributes to our
codebase. Commit messages and PR titles should be prefixed with a standard
code the states what kind of change it is. They fall broadly into 3 categories:
BUG (bug), and
SUPP (support). The
category has some more fine-grained aliases that you can use, such as
CI (continuous integration),
Maintainers generally perform two roles, merging PRs and making official releases.
We have a CLI script that will merge Pull Requests automatically once they have
been reviewed and approved. See the help message in
full details. If you have two-factor authentication turned on in Github, you
will have to generate an application-specific password by following this
You will then use that generated password on the command line for the
Access the Ibis "Merging PRs" wiki page for more information.
Access the Ibis "Releasing" wiki page for more information.