<commit_before># Contributor Guidelines

## General Process

1. Create a branch from the current version
2. Add commits for your changes
3. Open a pull request on Github

## Specifics

* Code should follow existing code standards i.e. line spacing, indenting, and naming conventions.
* Rebase commits for easier readability for code reviews
* When submitting your pull request, please be detailed in the description. At the minimum the request should contain the following:
	* Summary of the changes done (including changes to licenses)<commit_msg>Fix contributor doc<commit_after># Contributor Guidelines

## General Process

1. Create a fork from the current version
2. Add commits for your changes
3. Open a pull request on Github

## Specifics

* Code should follow existing code standards i.e. line spacing, indenting, and naming conventions.
* Rebase commits for easier readability for code reviews
* When submitting your pull request, please be detailed in the description. At the minimum the request should contain the following:
	* Summary of the changes done (including changes to licenses)
{'fraction_non_alphanumeric': 0.045454545454545456, 'fraction_numerical': 0.005454545454545455, 'mean_word_length': 4.7643979057591626, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, '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': '4352227', 'n_tokens_mistral': 267, 'n_tokens_neox': 251, 'n_words': 155}