<commit_before># How to contribute

Bug reports in the issue tracker and pull requests are welcome.

## Pull request
1. Fork the repository at github.
2. Clone your fork.

  ```
  $ git clone https://github.com/YOUR_GIT_USERNAME/cam_acq.git
  $ cd cam_acq
  ```
3. Add the main repository as upstream.

  ```
  $ git remote add upstream https://github.com/CellProfiling/cam_acq.git
  ```
4. Fetch dev branch from upstream and checkout to a local branch.

  ```
  $ git fetch upstream dev
  $ git checkout dev
  ```
5. Create a topic branch based off dev branch.

  ```
  $ git checkout -b cool_new_feature dev
  ```
6. Make your changes in the new topic branch. New features should preferably be accompanied with new tests. [PEP8](https://www.python.org/dev/peps/pep-0008/) and [PEP257](https://www.python.org/dev/peps/pep-0257/) style should be followed. We use [pylint](https://www.pylint.org/) and [flake8](http://flake8.pycqa.org/en/latest/) as code linters.
7. Test with tox and make sure existing tests don't fail. Linting will also be checked when tox is run.

  ```
  $ pip3 install tox
  $ tox
  ```
8. Add and commit your work and describe the additions and or changes in the commit message. Use an editor for the commit message, not the command line. Try to keep the header of the commit message within 50 characters and the body within 72 characters per line. A blank line should separate the header from the body of the commit message. Markdown is cool.

  ```
  $ git add -A
  $ git commit
  ```
9. Push you local changes to your fork.
<commit_msg>Fix typo in contributing instruction (#22)<commit_after># How to contribute

Bug reports in the issue tracker and pull requests are welcome.

## Pull request
1. Fork the repository at github.
2. Clone your fork.

  ```
  $ git clone https://github.com/YOUR_GIT_USERNAME/cam_acq.git
  $ cd cam_acq
  ```
3. Add the main repository as upstream.

  ```
  $ git remote add upstream https://github.com/CellProfiling/cam_acq.git
  ```
4. Fetch dev branch from upstream and checkout to a local branch.

  ```
  $ git fetch upstream dev
  $ git checkout dev
  ```
5. Create a topic branch based off dev branch.

  ```
  $ git checkout -b cool_new_feature dev
  ```
6. Make your changes in the new topic branch. New features should preferably be accompanied with new tests. [PEP8](https://www.python.org/dev/peps/pep-0008/) and [PEP257](https://www.python.org/dev/peps/pep-0257/) style should be followed. We use [pylint](https://www.pylint.org/) and [flake8](http://flake8.pycqa.org/en/latest/) as code linters.
7. Test with tox and make sure existing tests don't fail. Linting will also be checked when tox is run.

  ```
  $ pip install tox
  $ tox
  ```
8. Add and commit your work and describe the additions and or changes in the commit message. Use an editor for the commit message, not the command line. Try to keep the header of the commit message within 50 characters and the body within 72 characters per line. A blank line should separate the header from the body of the commit message. Markdown is cool.

  ```
  $ git add -A
  $ git commit
  ```
9. Push you local changes to your fork.

{'fraction_non_alphanumeric': 0.0942258883248731, 'fraction_numerical': 0.018083756345177664, 'mean_word_length': 3.3670360110803323, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 10, 'lorem ipsum': 0, 'www.': 6, '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': '6909676', 'n_tokens_mistral': 1002, 'n_tokens_neox': 928, 'n_words': 429}