Skip to content

Latest commit

 

History

History
76 lines (50 loc) · 2.8 KB

CONTRIBUTING.rst

File metadata and controls

76 lines (50 loc) · 2.8 KB

Contributing

Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given. The following helps you to start contributing specifically to pyrato. Please also consider the general contributing guidelines for example regarding the style of code and documentation and some helpful hints.

Types of Contributions

Report Bugs or Suggest Features

The best place for this is https://github.com/pyfar/pyrato/issues.

Fix Bugs or Implement Features

Look through https://github.com/pyfar/pyrato/issues for bugs or feature request and contact us or comment if you are interested in implementing.

Write Documentation

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

Get Started!

Ready to contribute? Here's how to set up pyrato for local development using the command-line interface. Note that several alternative user interfaces exist, e.g., the Git GUI, GitHub Desktop, extensions in Visual Studio Code ...

  1. Fork the pyrato repo on GitHub.

  2. Clone your fork locally and cd into the pyrato directory:

    $ git clone https://github.com/YOUR_USERNAME/pyrato.git
$ cd pyrato

  3. Install your local copy into a virtualenv. Assuming you have Anaconda or Miniconda installed, this is how you set up your fork for local development:

    $ conda create --name pyrato python
$ conda activate pyrato
$ conda install pip
$ pip install -e .
$ pip install -r requirements_dev.txt

  4. Create a branch for local development. Indicate the intention of your branch in its respective name (i.e. feature/branch-name or bugfix/branch-name):

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

    Now you can make your changes locally.

  5. When you're done making changes, check that your changes pass ruff and the tests:

    $ ruff check
$ pytest

    ruff must pass without any warnings for ./pyrato and ./tests using the default or a stricter configuration. Ruff ignores a couple of PEP Errors (see ./pyproject.toml). If necessary, adjust your linting configuration in your IDE accordingly.

  6. 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

  7. Submit a pull request on the develop branch through the GitHub website.