<commit_before># Contributing

Contributions of any kind are most welcome! Just open an [issue](https://github.com/PROGRADE-Tech/Tarchivebot/issues/new) or send a [pull request](https://github.com/PROGRADE-Tech/Tarchivebot/compare). All code contributions will be licensed under the [GNU AGPL-3.0](https://github.com/PROGRADE-Tech/Tarchivebot/blob/master/LICENSE).

## Pull requests

You can use whatever tool you feel most comfortable with to develop your feature. However we do encourage you to use the Git command line interface. Here are the steps to submitting a PR using the CLI:

1. Click the fork button on the [Tarchivebot repository](https://github.com/PROGRADE-Tech/Tarchivebot).
2. Clone your fork to your local machine: `git clone https://github.com/{{your_username}}/Tarchivebot.git && cd Tarchivebot`
3. Create your branch and name it after the related issue or feature `git checkout -b {{feature_name}}`
4. Now you can start coding your feature and changes.
5. After you're done commit your changes. `git commit -am "{{commit_message}}"`. Signed commits are also very much appreciated: `git commit -S -m "{{commit_message}}"`.
6. Push your changes to your fork: `git push origin -b {{feature_name}}`
7. Go to your fork on GitHub and create the pull request!

## Style guidelines

We're not at all strict about any particular coding standard. However you can take a look at [Javascript Standard Style](https://github.com/feross/standard/blob/master/RULES.md) if you need a general styling or formatting guideline to adhere to.

## Difficulties

If you happen to experience any technical difficulties during the contribution process feel free to [create an issue](https://github.com/PROGRADE-Tech/Tarchivebot/issues/new) and we'll try to help out.<commit_msg>Changed style guideline section to reflect possible future guidelines.<commit_after># Contributing

Contributions of any kind are most welcome! Just open an [issue](https://github.com/PROGRADE-Tech/Tarchivebot/issues/new) or send a [pull request](https://github.com/PROGRADE-Tech/Tarchivebot/compare). All code contributions will be licensed under the [GNU AGPL-3.0](https://github.com/PROGRADE-Tech/Tarchivebot/blob/master/LICENSE).

## Pull requests

You can use whatever tool you feel most comfortable with to develop your feature. However we do encourage you to use the Git command line interface. Here are the steps to submitting a PR using the CLI:

1. Click the fork button on the [Tarchivebot repository](https://github.com/PROGRADE-Tech/Tarchivebot).
2. Clone your fork to your local machine: `git clone https://github.com/{{your_username}}/Tarchivebot.git && cd Tarchivebot`
3. Create your branch and name it after the related issue or feature `git checkout -b {{feature_name}}`
4. Now you can start coding your feature and changes.
5. After you're done commit your changes. `git commit -am "{{commit_message}}"`. Signed commits are also very much appreciated: `git commit -S -m "{{commit_message}}"`.
6. Push your changes to your fork: `git push origin -b {{feature_name}}`
7. Go to your fork on GitHub and create the pull request!

## Style guidelines

We don't yet enforce any particular coding style. However we will probably look into following [Javascript Standard Style](https://github.com/feross/standard/blob/master/RULES.md) in the future. You can use that standard as a general guideline for your code.

## Difficulties

If you happen to experience any technical difficulties during the contribution process feel free to [create an issue](https://github.com/PROGRADE-Tech/Tarchivebot/issues/new) and we'll try to help out.
{'fraction_non_alphanumeric': 0.0918141592920354, 'fraction_numerical': 0.00497787610619469, 'mean_word_length': 4.687106918238993, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 14, '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': '2588623', 'n_tokens_mistral': 1010, 'n_tokens_neox': 959, 'n_words': 452}