<commit_before>===========================
How we handle contributions
===========================

We use git/Github to handle contributions.  If you're new to git, you may
appreciate `this guide <https://openhatch.org/wiki/Git_Basics#Create_pull_request>`_.

As a pull request submitter
===========================

Creating a pull request
~~~~~~~~~~~~~~~~~~~~~~~

Get the latest version of master
################################

Before creating a pull request, update the master branch of your local
repository with the latest version of the OpenHatch-owned repository. In
git, you can achieve this by `developing on a branch`_ and rebasing your
branch commits on top of master with `git rebase master`_. You can also use
git rebase -i master for an interactive rebase, in which you can reorder
and edit commits. We prefer rebasing to merging because rebasing preserves
a linear commit history, which can be easier to keep track of and reason
about.

Test your changes
#################

    1. Add unit tests with your functionality changes or additions.
    2. Use docstrings and comments where appropriate. Spell-check your
       additions. Try to apply `pep8`_ standards.
    3. Test your changes on a local instance of the website. Prove to yourself
       that your changes address the issue they are supposed to address.
    4. Run the `test suite <internals/continuous_integration.html>`_, and make sure your unit tests pass and all tests that
       passed before your changes still pass.
    5. Use a tool like `PyChecker`_ to check for bugs.


.. _pep8: http://pypi.python.org/pypi/pep8
.. _PyChecker: http://pypi.python.org/pypi/PyChecker/0.8.12


Generate a pull request
#######################

Generate a pull request by pushing your changes to your personal remote.
You can then create a pull request to the OpenHatch repository. In the commit
message, include the issue the pull request addresses. For example: "Closes:
http://openhatch.org/bugs/issue398"

.. _developing on a branch: http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html#_managing_branches
.. _git rebase master: http://www.kernel.org/pub/software/scm/git/docs/git-rebase.html
.. _How to generate patches with git format-patch: https://openhatch.org/wiki/How_to_generate_patches_with_git_format-patch


Submitting a pull request
~~~~~~~~~~~~~~~~~~~~~~~~~

    1. Add a link to the pull request in the issue ticket at https://openhatch.org/bugs.
    2. Change the issue status to "need-review".
    3. Join IRC and say that you have an issue ready for review.
<commit_msg>Update url link in handling contributions doc<commit_after>===========================
How we handle contributions
===========================

We use git/Github to handle contributions.  If you're new to git, you may
appreciate `this guide <https://openhatch.org/wiki/Git_Basics#Create_pull_request>`_.

As a pull request submitter
===========================

Creating a pull request
~~~~~~~~~~~~~~~~~~~~~~~

Get the latest version of master
################################

Before creating a pull request, update the master branch of your local
repository with the latest version of the OpenHatch-owned repository. In
git, you can achieve this by `developing on a branch`_ and rebasing your
branch commits on top of master with `git rebase master`_. You can also use
git rebase -i master for an interactive rebase, in which you can reorder
and edit commits. We prefer rebasing to merging because rebasing preserves
a linear commit history, which can be easier to keep track of and reason
about.

Test your changes
#################

    1. Add unit tests with your functionality changes or additions.
    2. Use docstrings and comments where appropriate. Spell-check your
       additions. Try to apply `pep8`_ standards.
    3. Test your changes on a local instance of the website. Prove to yourself
       that your changes address the issue they are supposed to address.
    4. Run the `test suite <advanced/advanced_installation.html`_, and make sure your unit tests pass and all tests that
       passed before your changes still pass.
    5. Use a tool like `PyChecker`_ to check for bugs.


.. _pep8: http://pypi.python.org/pypi/pep8
.. _PyChecker: http://pypi.python.org/pypi/PyChecker/0.8.12


Generate a pull request
#######################

Generate a pull request by pushing your changes to your personal remote.
You can then create a pull request to the OpenHatch repository. In the commit
message, include the issue the pull request addresses. For example: "Closes:
http://openhatch.org/bugs/issue398"

.. _developing on a branch: http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html#_managing_branches
.. _git rebase master: http://www.kernel.org/pub/software/scm/git/docs/git-rebase.html
.. _How to generate patches with git format-patch: https://openhatch.org/wiki/How_to_generate_patches_with_git_format-patch


Submitting a pull request
~~~~~~~~~~~~~~~~~~~~~~~~~

    1. Add a link to the pull request in the issue ticket at https://openhatch.org/bugs.
    2. Change the issue status to "need-review".
    3. Join IRC and say that you have an issue ready for review.

{'fraction_non_alphanumeric': 0.13623188405797101, 'fraction_numerical': 0.006956521739130435, 'mean_word_length': 4.160518444666002, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 6, 'https://': 6, 'lorem ipsum': 0, 'www.': 4, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4931514', 'n_tokens_mistral': 1434, 'n_tokens_neox': 1360, 'n_words': 630}