Skip to content

Latest commit

 

History

History
75 lines (43 loc) · 1.85 KB

CONTRIBUTING.rst

File metadata and controls

75 lines (43 loc) · 1.85 KB

Contributing

Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given.

Get Started!

Ready to contribute? Here's how to set up pytest_merge_xml for local development.

  1. Fork the pytest_merge_xml repo on GitHub.

  2. Clone your fork locally:

    $ git clone git@github.com:your_github_username_here/pytest-merge-xml.git
  3. Create a virtual environment and activate it:

    $ python -m virtualenv .env
    
    $ .env\Scripts\activate  # For Windows
    $ source .env/bin/activate  # For Linux
  4. Install the development dependencies for setting up your fork for local development:

    $ cd pytest_merge_xml/
    $ pip install -e .[testing,docs]

    Note

    If you use conda, you can install virtualenv in the root environment:

    $ conda install -n root virtualenv

    Don't worry as this is safe to do.

  5. Install pre-commit:

    $ pre-commit install
  6. Create a branch for local development:

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

    Now you can make your changes locally.

  7. When you're done making changes, run the tests:

    $ pytest
  8. If you want to check the modification made on the documentation, you can generate the docs locally:

    $ tox -e docs

    The documentation files will be generated in docs/_build.

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