Contributions are welcome and greatly appreciated! Every little bit helps and credit will always be given. If you have any questions or want to get in touch with the core team feel free to join our Discord server.

You can contribute in many ways:

Types of Contributions

Report Bugs

Report bugs at

If you are reporting a bug, please:

  • Use the appropriate issue template.

  • Be as detailed as possible. The more time you invest into describing the bug, the more time we save solving them, effectively allowing us to improve cookietemple at a faster pace.

  • Be patient. We are passionate, hard workers, but also have demanding full time jobs, which require a lot of our attention.

Fix Bugs

Look through the GitHub issues for bugs. We would appreciate it if you quickly commented on the respective issue and write that you are working on this bug, to minimize the chances of two people working on the same task.

Implement Features

Look through the GitHub issues for features. The same rule also applies to features. Please write if you’re picking up one of the feature suggestions.

Add Templates

If you’re planning to add a new template to cookietemple we highly suggest that you open an issue using the corresponding template and discuss it first with us.
Adding new templates will guide you through the process of adding new templates to cookietemple.
Please ensure that you are following all the guidelines and that your template meets the requirements.

Write Documentation

cookietemple could always use more documentation, whether as part of the official cookietemple 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 here .

If you are proposing a feature:

  • Use the appropriate GitHub issue

  • 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 cookietemple for local development.

  1. Fork the cookietemple repo on GitHub.

  2. Clone your fork locally

$ git clone
  1. Install your local copy into a virtualenv. Assuming you have virtualenvwrapper installed, this is how you set up your fork for local development

$ mkvirtualenv cookietemple
$ cd cookietemple/
$ python develop

4. Create a branch for local development. Note that you should always start your branch name with either fix or feature so that the Release Drafter GitHub App will handle your PR right.

$ git checkout -b fix_or_feature/name-of-your-bugfix-or-feature

Now you can make your changes locally.

  1. When you’re done making changes, check that your changes pass the nox test suite.

$ nox

To get nox (and nox-poetry), just pip install them into your virtualenv.

  1. Commit your changes and push your branch to GitHub

$ git add .
$ git commit -m "Your detailed description of your changes."
$ git push origin fix_or_feature/name-of-your-bugfix-or-feature
  1. 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.rst, if it is a major feature.
  3. The pull request should work for Python 3.7+ and for PyPy. Check your pull request on Github and verify that all checks and GitHub workflows are passing!


To run a subset of tests:

.. code-block:: console

$ pytest tests/something