Skip to content

Latest commit

 

History

History
120 lines (78 loc) · 3.3 KB

CONTRIBUTING.rst

File metadata and controls

120 lines (78 loc) · 3.3 KB
Raw

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 https://github.com/phausamann/rigid-body-motion/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 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

rigid-body-motion could always use more documentation, whether as part of the official rigid-body-motion 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 https://github.com/phausamann/rigid-body-motion/issues.

If you are proposing a 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 rigid-body-motion for local development.

  1. Fork the rigid-body-motion repo on GitHub.

  2. Clone your fork locally:

    $ git clone [email protected]:your_name_here/rigid-body-motion.git

  3. The recommended way of setting up the project is in a conda environment:

    $ conda env create

  4. Create a branch for local development:

    $ 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 the tests:

    $ conda activate rbm
$ pytest

  6. The project uses black for code formatting, isort for import sorting and flake8 for linting. You can set up these checks as pre-commit hooks:

    $ conda activate rbm
$ conda install pre-commit
$ pre-commit install

    Note that the project currently uses black version 19.10b0.

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

  8. 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 HISTORY.rst.
  3. The pull request should work for Python 3.6, 3.7, 3.8 and 3.9. See the checks at the bottom of the pull request page to resolve any issues.

Deploying

A reminder for the maintainers on how to deploy. Make sure all your changes are committed (including an entry in HISTORY.rst). Then run:

$ bumpversion patch # possible: major / minor / patch
$ git push