https://github.com/o2r-project/geoextent.git
Raw File
Tip revision: 6aca93956d5cd6742318fd3ab27bb176b5f8c24b authored by Daniel NĂ¼st on 02 July 2020, 07:47:08 UTC
fix block quote in rst
Tip revision: 6aca939
CONTRIBUTING.md
# Contributing

We welcome [contributions of all kinds](https://opensource.guide/how-to-contribute/), be it code, tests, or documentation.
When contributing to this repository, please first discuss the change you wish to make by [opening an issue](https://github.com/o2r-project/geoextent/issues/new).

Check out the [existing issues](https://github.com/o2r-project/geoextent/issues/) for related or similar ideas and features.

**Please note we have a [code of conduct](CONDUCT.md), please follow it in all your interactions with the project.**

## How to contribute

The following steps assume you are familiar with Python packages.

We follow a _fork and pull_ development model. [Fork](https://help.github.com/en/articles/fork-a-repo), then clone the repo:

```bash
git clone https://github.com/o2r-project/geoextent.git
```

See the [development readme](https://o2r.info/geoextent/development.html) file for installation and running tests.
Make sure the tests pass before you start developing.

- Create a new feature branch from the current `master` branch.
- Make your change.
- Add documentation for your change.
- Add tests for your change.
- Make the tests pass, i.e. `pytest`
- Add yourself to the contributor list

Push your feature branch to your fork and [submit a pull request](https://help.github.com/en/articles/about-pull-requests) to the main repository's `master` branch.
Please be patient until maintainers review your pull request.
We may suggest some changes or improvements or alternatives.
Feel free to ping `@nuest` if you don't hear anything after a few weeks.
back to top