Skip to content

Latest commit

 

History

History
67 lines (44 loc) · 2.93 KB

CONTRIBUTING.md

File metadata and controls

67 lines (44 loc) · 2.93 KB

Contributing

General code rules

For docstrings, we're following Google's documentation conventions.

All methods meant to be used by end-user must be documented; no exceptions!

Submitting a pull request

Note: Every PR requires at least two reviews from at least two of the core review members. It won't be possible to merge changes without at least two approvals. List of members are available on Settings/Members page.

Before you submit your pull request, please consider the following guidelines:

  1. Fork the repository and clone your fork:

    1. Open the following URL in your browser: https://github.com/RedHatInsights/dvo-extractor/.

    2. Click on the "Fork" button (near the top-right corner).

    3. Open your forked repository in browser: https://github/YOUR-USERNAME/dvo-extractor/

    4. Click on the green "Clone or download" button and copy the clone URL of your fork of the repository.

    5. Clone the repository to get a local copy that you can edit:

      git clone REPOSITORY-URL

  2. Make your changes in a new git branch:

    git checkout -b bug/my-fix-branch master

  3. Create your patch, ideally including appropriate test cases.

  4. Make sure all your changes to Python code follow the pycodestyle guidelines. Aside from that, EditorConfig rules must be satisfied, not just for Python files, but also for all configuration files. You can check it using this Go utility or let your editor handle it for you (see the official documentation for more details).

  5. Include documentation that either describe a change to a behavior or the changed capability to an end user.

  6. Commit your changes using a descriptive commit message. If you are fixing an issue, please include something like "closes #xyz" or "fixes #xyz", where xyz is the number of the issue.

  7. Push your branch to GitHub:

    git push origin bug/my-fix-branch

  8. When opening a pull request, select the master branch as a base.

  9. Mark your pull request with [WIP] (Work In Progress) to get feedback but prevent merging (e.g. [WIP] Update CONTRIBUTING.md).

  10. If we suggest changes, then please:

    1. Make the required modifications.
    2. Push the changes to GitHub (this will automatically update your pull request) by either:

      • Adding a new commit and pushing:

        git commit
git push origin bug/my-fix-branch

      • Rebasing your branch and force-pushing:

        git rebase -i master
git push -f origin bug/my-fix-branch

That's it! Thank you for your contribution!